+erik2d2 Posted August 5, 2013 Share Posted August 5, 2013 The "last found" date which is shown e.g. in the list of owned caches is wrong. It is the found-date of the latest log and not the latest found-date. Usually it's the same. But not if someone logs a found which is some time ago. Quote Link to comment
+The A-Team Posted August 7, 2013 Share Posted August 7, 2013 The "last found" date which is shown e.g. in the list of owned caches is wrong. It is the found-date of the latest log and not the latest found-date. Usually it's the same. But not if someone logs a found which is some time ago. I was in the process of typing up that I wasn't seeing this when I realized that I am. This cache was most recently found on August 5, but the most recently-submitted log was the one by gussdog on August 3. On this list and on the list of my owned caches on my public profile, it shows the last find as being "August 3" and "4 days ago" respectively, which are both incorrect. Quote Link to comment
+Isonzo Karst Posted August 7, 2013 Share Posted August 7, 2013 I'm seeing that when a cacher deletes a found log, the find date remains. On my owned caches, I see: Well, It's a Beautiful Spot Date Last Found Sunday, August 04, 2013 A couple of found logs came in on that day, but must have been deleted by the cachers posting them. The last find on that is 04/16/2010 Quote Link to comment
Moun10Bike Posted August 8, 2013 Share Posted August 8, 2013 I've been able to reproduce the issue and have entered a bug into the queue. Quote Link to comment
+DanPan Posted August 8, 2013 Share Posted August 8, 2013 (edited) Same issue for GC41QJY Yestarday: "latest Found-it date" on cachelisting was 06/aug == "Date Last Found" on list my owned caches was 06/aug => OK Today: "latest Found-it date" on cachelisting is 06/aug =/= "Date Last Found" on list my owned caches is now 03/aug ... => NOK (due to a recently-submitted Found-it log of 03/aug) Edited August 8, 2013 by DanPan Quote Link to comment
+Sarah the Monkey Posted August 12, 2013 Share Posted August 12, 2013 I have a similar problem, in that my cache Aquila The Hun(t) has been found several times in August, but is displaying an old July date as the Last Found. This is really unhelpful as it doesn't reflect the accessibility of what it's a quite new but fairly frequently found cache. Makes it look like there's something wrong with it, which will make cache and dashers wary during the 31 days challenge. It's only this one cache too, which it's weird. Please can you mend it GS powers? Quote Link to comment
stebu Posted August 14, 2013 Share Posted August 14, 2013 The last update today/yesterday did not fix this. The "last found date" is still the date of the log that was last entered, not the date, when the cache was last found. This messes up my evaluation of caches to hunt based on the last found date. E.g. today I encountered a cache that indicates last found on Aug 5th 2008, although it should be Jan 1st 2013. The old log says "some forgotten fieldnotes, logging late" Quote Link to comment
+Harry Dolphin Posted August 14, 2013 Share Posted August 14, 2013 Especially strange on a mystery cache that is not found often. We logged 08/03/2013. Most recent log is 10/21/2011. Quote Link to comment
doshman Posted August 14, 2013 Share Posted August 14, 2013 Any update? I like finding lonely caches and this is cramping my plans for the weekend! Quote Link to comment
+===sgb Posted August 16, 2013 Share Posted August 16, 2013 "Me too". Several of my (93) caches have 2012 last found dates and at least some have been found this year. Quote Link to comment
+Cardinal Red Posted August 17, 2013 Share Posted August 17, 2013 If we could get accurate data, what do you suppose Groundspeaks customer satisfaction number would be? I'll go lower than 66% Jim. I'm an optimist. I can't risk logging a find to one of my own bogus find date caches right now (I'm currently on day 16 of a 31 day NO CACHES FOR ME streak) to check if that will correct the date. Could someone log a 06/11/2013 find to The POINT Of No Return for me? And then delete it of course. I suspect that should work. I also suspect I might have to fix any of my infrequently found ones, on my own, the same way. Is this part of Groundspeaks plan to make the game more fun and exciting? Quote Link to comment
+Vesuviano Posted August 19, 2013 Share Posted August 19, 2013 (edited) Hi, I have same problem for my owned caches, exactly as erik2d2; The "last found" date which is shown in the list of owned caches is wrong: It is the found-date of the latest log and not the latest found-date. Can you help me to fix? Thanks in advance Edited August 19, 2013 by Vesuviano Quote Link to comment
meatmachine Posted August 19, 2013 Share Posted August 19, 2013 Came here to post this, glad to see it was already done! My own cache was last found August 10, and it showed that up until about a week ago when it suddenly changed to May 26. It still says May 26 as does another cache close by (that has also been found this month). Others in the area seem to be up-to-date, but mine and another close by magically changed to May 26th. Hoping this gets fixed! Also, it shows this on here and on the iPhone app. Quote Link to comment
+Cardinal Red Posted August 21, 2013 Share Posted August 21, 2013 I still have several (I own) wrong 'last found date' caches, but the oldest nearby wrong date cache (I do not own) just got a Find log today. The 'last found date' is now correct. I fear this Bug will be given a very low priority for three reasons. #1. There is no money in it. #2. Groundspeak doesn't even care enough to provide any follow up comment beyond acknowledging the Bug (see reason #1). #3. We can fix it ourselves, over time, one cache at a time. Looks like I will be creating a cache maintenance sock puppet account. Just need to think of a good name. Give me a minute. Quote Link to comment
+Team Pixie Posted August 23, 2013 Share Posted August 23, 2013 When I try to search for the caches in Belgium that have not been found in the last years (http://www.geocaching.com/seek/nearest.aspx?country_id=4&as=1&sortdir=asc&sort=lastfound), often the date of the first log is listed instead of the date of the most recent log... Quote Link to comment
+Vesuviano Posted August 23, 2013 Share Posted August 23, 2013 I've been able to reproduce the issue and have entered a bug into the queue. Hi Moun10Bike, do you know if anybody has started to work on the issue? are there many issues in the queue to work before this one? Cheers Vesuviano Quote Link to comment
Moun10Bike Posted August 23, 2013 Share Posted August 23, 2013 This issue should now be corrected; however, the correct date will not show up until a new log is posted on any given cache to update it. Quote Link to comment
+Vesuviano Posted August 24, 2013 Share Posted August 24, 2013 This issue should now be corrected; however, the correct date will not show up until a new log is posted on any given cache to update it. Thanks a lot Moun10Bike! Quote Link to comment
+JL_HSTRE Posted August 28, 2013 Share Posted August 28, 2013 Looks like the fix worked. I came across a cache that was published in 2013, but the website said it was Last Found in 2002! I logged a Note (then deleted it) and the cache no longer had the bogus date. Quote Link to comment
+edhamster Posted August 28, 2013 Share Posted August 28, 2013 (edited) Looks like I am possibly still seeing this problem, not only with caches I own but others I plan on seeking. For example my L.O.L. cache (http://coord.info/GC3NNGJ)under a search shows it was last found on May 26, 2013 but upon looking at the cache's page it shows that it was last found/logged on Aug. 14, 2013. I have also seen this same issue for many other caches that display different last found dates under a search and then under the cache's page itself. **So I just reread the post about the resolution of the issue so this looks like it has been resolved. Guess I need to wait for another found log to be posted to see if the last found date changes. Edited August 28, 2013 by edhamster Quote Link to comment
+_SWH Posted August 31, 2013 Share Posted August 31, 2013 Does anyone know when this will be fixed? There are several of us who like to go hunt lonely caches rather than first to find. Hard to do if list is incorrect.... Quote Link to comment
+Team Bullis Posted September 1, 2013 Share Posted September 1, 2013 I have just discovered this very issue on the NH page. Click on Newest in NH or PLAY Hide n Seek and then choose New Hampshire. Then click on Last Found, now do it again so that all the unfounds are listed. On the next page at the bottom of the ones that haven't been found, are the caches that haven't been found in a long time. Look at The King's Locked Gates for example. It says it hasn't been found since 2010, now click onto the cache. It's been found a lot recently. Most, if not all, of the multis are like this. 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.