There are a lot of moving parts to this one. Hope I don't get anyone more confused than I am.
Went caching Sunday and Monday. Came home tired both days. Dumped the info from the GPSr into GSAK, and populated the Publish Logs page. Too tired to go through and write the logs right away.
Later in the evening, I wrote a couple of logs. I could have waited until I'd written them all before transmitting, but I wanted to get these out right away. Something about watching that find count increment. So I transmitted the first one, wrote the second one, then transmitted it. Then I went to the cache pages on gc.com. None of what I wrote went through, only the boilerplate text that was on the template. So I deleted both the logs through the website. My find count decremented appropriately.
I went back into GSAK and Publish Logs and discovered that the text I had added to the log had been discarded. I thought that clicking "OK" after writing would save that text, but somehow it got sent to the bin. This happened for both the logs that got transmitted with the wrong info.
Somewhere in here I look through the forums and find that there has been a patch to fix a Publish Logs problem. So I update from patch .39 to patch .41.
Now, I try to redo my logs through GSAK. I find the listings in the Publish Logs page (had to uncheck the "Show only unpublished logs" box to do that), write my new content and try to transmit. The error was something about can't publish that log twice, and you have to clone it first. OK, fine, I don't get that, but I hit the clone button, find the new listing, and start typing again. Get done, transmit that one, then the other one, and run the GenUploadStats macro.
That page now reports that I have two more finds than I actually have. I don't have a clue how it got those counts, except that I expect it is still counting those two logs that I deleted. Oh, and somehow it's gotten the finds out of order. In the milestones list, where it displays the name of the last cache found, it's not correct. I think the PL sequence number of one of the revised cache logs is higher than the one for a cache that was actually found later. Ergo, if my logic is correct, it shows the wrong cache at the end of the string.
What does anyone suppose has happened here, and what can I do in GSAK to make either FSG or GUS figure out my correct number of finds and in the correct order?
I imagine that I've left out some critical details in my explanation, so if there's further information deemed necessary, I'll be happy to fill in where I can.
Went caching Sunday and Monday. Came home tired both days. Dumped the info from the GPSr into GSAK, and populated the Publish Logs page. Too tired to go through and write the logs right away.
Later in the evening, I wrote a couple of logs. I could have waited until I'd written them all before transmitting, but I wanted to get these out right away. Something about watching that find count increment. So I transmitted the first one, wrote the second one, then transmitted it. Then I went to the cache pages on gc.com. None of what I wrote went through, only the boilerplate text that was on the template. So I deleted both the logs through the website. My find count decremented appropriately.
I went back into GSAK and Publish Logs and discovered that the text I had added to the log had been discarded. I thought that clicking "OK" after writing would save that text, but somehow it got sent to the bin. This happened for both the logs that got transmitted with the wrong info.
Somewhere in here I look through the forums and find that there has been a patch to fix a Publish Logs problem. So I update from patch .39 to patch .41.
Now, I try to redo my logs through GSAK. I find the listings in the Publish Logs page (had to uncheck the "Show only unpublished logs" box to do that), write my new content and try to transmit. The error was something about can't publish that log twice, and you have to clone it first. OK, fine, I don't get that, but I hit the clone button, find the new listing, and start typing again. Get done, transmit that one, then the other one, and run the GenUploadStats macro.
That page now reports that I have two more finds than I actually have. I don't have a clue how it got those counts, except that I expect it is still counting those two logs that I deleted. Oh, and somehow it's gotten the finds out of order. In the milestones list, where it displays the name of the last cache found, it's not correct. I think the PL sequence number of one of the revised cache logs is higher than the one for a cache that was actually found later. Ergo, if my logic is correct, it shows the wrong cache at the end of the string.
What does anyone suppose has happened here, and what can I do in GSAK to make either FSG or GUS figure out my correct number of finds and in the correct order?
I imagine that I've left out some critical details in my explanation, so if there's further information deemed necessary, I'll be happy to fill in where I can.