Log dates out of order?

[+Pharmadude]

This bug

Bob

has its most recent log dated 11/20/08, and it is placed above logs from 2009. How is this possible?

I thought all logs are automatically sorted by date.

[+BlueDeuce]

This is the second report I've seen on this.

 

http://www.geocaching.com/track/details.aspx?id=2184576

[+NanCycle]

re TB "Bob" -- interesting that on 11/20/08 it was in Washington, but the log in question here is a "Discovered" at its current location in Utah. Something is "fishy" about the log date.

[+EscapeFromFlatland]

Yeah, I have a few trackables showing 07/20/09 after 08/01/09.

[+Eartha]

Moving to the geocaching.com website forums. This is a website issue.

[+NanCycle]

Just saw "out of order dates" on another TB. Evidently they are being sorted according to the dates the logs were actually posted, rather than the dates that appear on the logs.

[jholly]

Just saw "out of order dates" on another TB. Evidently they are being sorted according to the dates the logs were actually posted, rather than the dates that appear on the logs.

 

I would agree with that. I wonder if trackable logs are like cache logs and have a unique log ID and the bug page sorts by ID and not the date in the log. I can certainly see sorting by logID since it would be easier and is not dependent on interpreting dates. (basically what Doublebent said, but lots of times there are things under the covers that is not evident.)

 

Jim

Edited September 3, 2009 by jholly

[+fsafranek]

I've got something similar going on. After I added a thread on this elsewhere I took another look. The dates haven't changed but they are no longer listed in chronological order and several Discovery logs from different people here in San Diego area (and a couple in Utah) now point to the same cache in Kansas which is totally bogus and an impossibility. The data is corrupt I guess?

 

I added a vehicle TB sticker to my Jeep this summer and drove it from the San Diego area to Kansas and back (yea, stopped at Mingo). I dipped it along the way ("dropped" it in when I logged a cache find and then grabbed it back right away) to record the progress. That worked fine and showed the route I took for the trip. As mentioned above, a few people have also discovered it in the meantime.

 

But when I looked at it yesterday I noticed that everything is screwed up. The map looks like I zig-zagged back and forth between California and Kansas. And the resulting mileage is crazy also. Not sure when this actually happened because I don't look at it every day.

 

TB2K16T

Edited September 6, 2009 by fsafranek

[+dlgps]

I am running into the same thing while logging our finds on our two-week camping trip. Groundspeak: PLEASE fix this!!!!

[+fsafranek]

Looks like they got it sorted out. Thank you Groundspeak!!!