| QUOTE (Kai Team @ December 26, 2013 09:41 am) | ||
| OK. Sorry I'm being dense on this, but I need to clarify some more things: 1) is the correct find number appearing in the log generated by Publish Logs? In other words, does the Published Log show the correct find count, but an incorrect number is being copied to your custom field, or is the %Count tag putting the wrong number in the log itself? 2) when you published your found log on this cache, did you use the date you completed the challenge, of did you back date the found log to the date of your note?
3) Where is the found count one less that your actual total? In Publish Logs, in your custom field, at Geocaching.com, all three? |
1) is the correct find number appearing in the log generated by Publish Logs? In other words, does the Published Log show the correct find count, but an incorrect number is being copied to your custom field, or is the %Count tag putting the wrong number in the log itself?
No. The first cache that I found is the same as the last cache that I found on my previous batch of logs. These find number had to be corrected with Fillfinds so that the numbers would be correct. For example I made on find today and when I run Publish Logs the Find Num is listed at 7945 which is the same as the last find I made yesterday.
2) when you published your found log on this cache, did you use the date you completed the challenge, of did you back date the found log to the date of your note?
I used the date that I finished the challenge which was 12/14/13.
3) Where is the found count one less that your actual total? In Publish Logs, in your custom field, at Geocaching.com, all three?
I am saying this because when I run Publish Logs the find number is one less than it should be. For example it was 7945 for my find today but it should be 7946 which is what my correct find total.
To correct this problem I have been removing the find number generated when I do my Publish Logs and then move the finds into my Finds Database and then run Fillfinds which generates the correct find numbers.
I really don't know if the updated challenge cache was the problem since someone else seems to be having a problem as well.