Displayed order of logged visits has changed

[+PlasmaWave]

Until recently a logged visit for a cache submitted using an App was displayed on the cache page in advance of local time (e.g. -8 hours for UK), so the logged date would appear before the publication date if it were before midnight Seattle time.

 

Recently that situation has changed, presumably to avoid the issue described, however this now means that on-line website logs submitted (for UK) up to 8 hours AFTER an App log are displayed before the App log. I have logged first-to-find logs for several newly published caches recently via an App, only to find much later in the day subsequent finders logs submitted on-line via the website are displayed before my much earlier log. I tested this a couple of times in the field by logging via the website instead of the App, which confirmed this change.

 

You might say, "well log via the website if it matters to you" ... yes it's true, that would work and show the correct logging "order", BUT it is difficult logging on a phone at GZ via the website - much easier with an App.

 

Geocaching.com appear to have made a change, which has created the same problem as before but in 'reverse' - in my mind, that is not a good solution.

 

Could Groundspeak take another look at this issue and hopefully think of cachers who are NOT on Seattle time? Not sure why an App submitted log cannot be adjusted for the local time difference from Seattle and then be displayed correctly.

 

Would be interested to hear from geocaching.com experts

[+The A-Team]

Could Groundspeak take another look at this issue and hopefully think of cachers who are NOT on Seattle time? Not sure why an App submitted log cannot be adjusted for the local time difference from Seattle and then be displayed correctly.

AFAIK, logs submitted via the API have always been timestamped with the current UTC time. The problem is that logs submitted through the website don't get such a timestamp and are instead tagged with a default time. This used to be midnight Seattle time, but that seems to have changed recently and is causing the change in display order. Regardless of whether they keep the current behaviour or revert to the previous behaviour, the logs won't be displayed in the correct order. The only way that can be fixed is if all logs are timestamped with the current UTC time (or the relevant time zone-adjusted time if logging from field notes).

[+dprovan]

Regardless of whether they keep the current behaviour or revert to the previous behaviour, the logs won't be displayed in the correct order. The only way that can be fixed is if all logs are timestamped with the current UTC time (or the relevant time zone-adjusted time if logging from field notes).

Well, that depends on what you consider "the right order". I was perfectly happy with the right order being the order they were posted to GC.com, but that's exactly what we don't get anymore.

[+PlasmaWave]

I realised I probably should have posted this under "Reported Bugs", so added the issue there and gave more info including tests I carried out (with screen shots). I too understood how the order worked previously and managed with it, but the recent change has not only added more confusion to the "order issue", BUT worse we in UK are seeing logs submitted via the geocaching.com website for NEWLY published caches (i.e. quick FTFs) are shown BEFORE the reviewer's published log! Now that is plain crazy. I show one example in that post where I managed joint FTF with two other folks ... the two logs sent from a Mobile App (PlasmaWave and NottsWalker) appear in correct order after the reviewer's log, but the third (Baira) sent his on-line from the geo-website and it is displayed before the reviewer's log. This was evening (about 20:00) in UK, so around midday Seattle Time. I have now seen the first logs being displayed before the reviewer's log quite a few times, so the above example was not a freak case.

 

Take a look at my other post:

 

http://forums.Groundspeak.com/GC/index.php?showtopic=341239&st=0&gopid=5611332entry5611332