+bertuz Posted June 5, 2013 Share Posted June 5, 2013 (edited) Hi! I found 7 caches in 2nd June. I logged the two first caches that I found the same day, 2n June. Today, 5th June, I logged the 5 other caches (geocaching.com date selector format is new!) What happens? The 2 first caches appears in the list like the 2 last caches! My milestone number 300 is wrong, and the order of the last 7 caches too! It's like: <-(older) 3rd,4th,5th,6th,7th,1st,2nd (new)-> Maybe it's for the last update in geocaching.com website (changes in the date selector format in the register page of a new found). Edited June 5, 2013 by bertuz Quote Link to comment
Pup Patrol Posted June 5, 2013 Share Posted June 5, 2013 Hi! I found 7 caches in 2nd June. I logged the two first caches that I found the same day, 2n June. Today, 5th June, I logged the 5 other caches (geocaching.com date selector format is new!) What happens? The 2 first caches appears in the list like the 2 last caches! My milestone number 300 is wrong, and the order of the last 7 caches too! It's like: <-(older) 3rd,4th,5th,6th,7th,1st,2nd (new)-> Maybe it's for the last update in geocaching.com website (changes in the date selector format in the register page of a new found). You can edit your milestones: http://www.geocaching.com/my/statistics_edit.aspx B. Quote Link to comment
+bertuz Posted June 5, 2013 Author Share Posted June 5, 2013 (edited) Thanks Pup Patrol! I successfully changed my milestone! The ordenation bug is still ON. Edited June 5, 2013 by bertuz Quote Link to comment
Pup Patrol Posted June 5, 2013 Share Posted June 5, 2013 Thanks Pup Patrol! I successfully changed my milestone! The ordenation bug is still ON. No problem. It's a little known thing, I think, and I only learned about it through the forums. But, yeah, the order thing is still a problem. B. Quote Link to comment
+bertuz Posted June 6, 2013 Author Share Posted June 6, 2013 Hi? Nobody (from geocaching.com) is checking the bug? Quote Link to comment
Moun10Bike Posted June 6, 2013 Share Posted June 6, 2013 I have confirmed that the timestamp on logs posted since the last site release is inconsistent with how we've been doing it for the last 13 years. I've entered a bug for engineering to investigate. Quote Link to comment
+bertuz Posted June 7, 2013 Author Share Posted June 7, 2013 Ok! Thanks Moun10Bike! The users who found bugs in the geocaching website should be rewarded with a free premium membership! Quote Link to comment
+TOcowboy Posted June 11, 2013 Share Posted June 11, 2013 Concerning the new software program regarding the logging of finds; if one has posted a log noting a "final find" for that day, all is good, as that final find log stays the same at the end. However, if one should work thru a "Milestone" and post a log as such, then at a future time, adds a prior missed log find to that date, the "Milestone" find goes out of order in the sequence and is changed from the proper one as noted in the posting. Is that the way it's going to be now? Quote Link to comment
+bertuz Posted June 18, 2013 Author Share Posted June 18, 2013 Moun10Bike, are there any news from the bug you've entered for engineering to investigate? Any sollution? Thanks Quote Link to comment
Moun10Bike Posted June 18, 2013 Share Posted June 18, 2013 The issue was corrected on June 11. Timestamps on logs posted to the web site are now back to the same time that they used to be prior to the last release. There will still be issues if you mix logs from the web site with those from an API-enabled app. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.