wrong (?) "Found On" date in list of a friend

[+teddy.66]

I use the list "Geocaches Found (All Geocache Finds)" of a friend with descending order on "Found On"

Please look at the screenschot. She found the GC with the red underlined date  on 09/May/2021.

But the listed date (24/May/2021) is not her found date but the last found date of the GC logged by another cacher.

 

Is this a bug or a feature ?

 

[+Bl4ckH4wkGER]

The "Found On" date on new Search indicates the date the cache was last found by anybody.

 

That said, the "All Geocaches Found" results are still sorted by the order that the player has found the caches.

 

I hope that makes sense.

[+GeoTrekker26]

While you made it clear, it doesn't make sense. When looking at a list related to a single user, one would expect the information would also relate to that user.  If this isn't corrected, the column header should be changed to reflect what is being displayed.

[+Hynz]

28 minutes ago, Bl4ckH4wkGER said:

I hope that makes sense.

Actually no 

I'm learning here (beeing currently a Basic Member and can not enjoy this new list) that on this new list not only *my* eventually found date is missing but it is also missing the date when the cacher *I'm looking at* has found the cache. Seriously?

[+HHL]

2 hours ago, teddy.66 said:

is not her found date but the last found date of the GC logged by another cacher.

Yes, use an appropriate link instead:

https://www.geocaching.com/seek/nearest.aspx?ul=TeamHeiDie

 

I'd recommend using this "quasi standard" Geocaching Dashboard:

http://www.geocachingadmin.com/search.pl

 

Hans

Edited May 28, 2021 by HHL

[+Bl4ckH4wkGER]

Thanks for the feedback. We will investigate opportunities to adjust what found date data is displayed or make the labels more clear.

[+CachingFoX]

Hi Bl4ckH4wkGER,

 

I think new search based "All Geocache Finds" contains a bug.

 

On 5/28/2021 at 5:47 PM, Bl4ckH4wkGER said:

The "Found On" date on new Search indicates the date the cache was last found by anybody.

 

Sure? I think it is not 100% clear what "Found On" means. It depends on the context of the search. If you don't know the context of the search, you are not able to say what kind of date "Found On" contains. Whether this is good or bad from UEX's perspective is also a matter of personal preference. From a technical perspective I would say is good, from a user's perspective I would say bad.

 

I see three search contexts

• Normal search: "Date of the last found by anybody" (ok)
• "All Geocache Finds" on MY public profile: "Date of my found" (ok)
• "All Geocache Finds" on FOREIGN public profiles: ???

Behaviour on foreign profiles

The "Found On" field has a strange behaviour on foreign public profiles:

•  for the first 50 results "Date of found by the user" (ok)
•  for the +50 (loaded) results "Date of the last found by anybody" (NOT ok)

I think this is a bug - or a secret feature? ;-) . But by the way, sorting of results (found date of the user) is still ok.

 

See attached picture, the "Found On" timeline has a (huge) gap. I create the picture from a profile of a very well known person and I know there is no such huge gap in their founds.

 

Reproduce the bug

• Open a public profile (with an long caching history) - not yours
• Go to Geocaches and open "All Geocache Finds"
• (optional) Change search order of "Found on" to ascend - do this and you can see the bug better
• Scroll down to the next loaded results (+50)

Cheers

CachingFoX

 

 

 

 

 

[+Muddy Woodies]

Have noticed this issue and it seems exactly as CachingFoX describes - our list fine, other users  display 'last found' after first 50. Displaying from oldest to latest behaves in a similarly incorrect manner.

I normally use Chrome, but the problem is also present with IE, which is often a fix for strange behavior on many websites.

Would strongly suspect that this is a bug, so it can be fixed......

[+balu2003]

It's a bug.
the first search results show the found date of the User you use in the search.
That is certainly also the intention of the developers, because they calles the URL and use FoundDateOfFoundByUser
 

https://www.geocaching.com/play/search?fb=TeamHeiDie&a=0&sort=FoundDateOfFoundByUser&asc=False

 

Look at the Cache https://www.geocaching.com/geocache/GC99V1Z

The last Found by any User is from MuggelM 17.06.2021
TeamHeiDie found it o 13.06.2021
And in the response to this search, the html shows in data-rownumber=\"26\"

<td class="pri-4" data-column="FoundDateOfFoundByUser">
     13.06.2021
</td>

Until now, its  OK, In the html you can see that data-rownumber goes from 0 to 49 (50 caches oer list entries)

If you scroll down, and the next 50 entries are loaded by the script, which creates this search to load the next entries, starting with the index 50.
 

https://www.geocaching.com/play/search/more-results?fb=TeamHeiDie&a=0&sort=FoundDateOfFoundByUser&asc=False&startIndex=50&selectAll=false
next from 100 to 149
https://www.geocaching.com/play/search/more-results?fb=TeamHeiDie&a=0&sort=FoundDateOfFoundByUser&asc=False&startIndex=100&selectAll=false

Now the response ist like this
 

class=\"pri-4\" data-column=\"DateLastVisited\"\u003e\n20.06.2021

 

 

You can clearly see:
the first 50 results have the data-column "FoundDateOfFoundByUser"
all next calls have the data-column "DateLastVisited

Lets call Data-Row Number 26 (that is data-id=\"GC99V1Z\" data-name=\"Am Teich

https://www.geocaching.com/play/search/more-results?fb=TeamHeiDie&a=0&sort=FoundDateOfFoundByUser&asc=False&startIndex=26&selectAll=false

Now you get instead of 13.06.2021 the date:

data-column=\"DateLastVisited\"\u003e\n17.06.2021

 

So theBug is, that play/search?fb gets an other result as /play/search/more-results?fb

 

This is a bug
 

 

[+balu2003]

@Bl4ckH4wkGER

I think your develepers should read this, because it is a bug, when the first 50 results of an query use an other  data-column than the following results
In Detail see above:

that your script in  play/search?fb gets an other result as the following calls to play/search/more-results?fb

 

[+teddy.66]

Thanks to CachingFoX and balu2003 for your investigation and confirmation, that this behavior is a BUG.

 I hope, that the developers will accept that an fix it.

 

[+Chrysalides]

I came to the forums to report this bug, and noticed that this thread has already been created a month ago. And it's definitely a bug, as noted by @balu2003 - the first 50 entries are correct in showing "found by user X" and the remainder shows "last found".

 

Anyone know of a workaround? I tried the old URL https://www.geocaching.com/seek/nearest.aspx?ul=XXXXX which seems to work, but I couldn't figure out how to filter by cache type.

 

Edit: I found that using https://www.geocaching.com/seek/nearest.aspx allows you to use cache type as filter, but it only works for the first page of 20 results. Subsequent pages are not filtered.

Edited June 30, 2021 by Chrysalides

[+balu2003]

that is an other bug, I can confirm it:
 

Quote

Edit: I found that using https://www.geocaching.com/seek/nearest.aspx allows you to use cache type as filter, but it only works for the first page of 20 results. Subsequent pages are not filtered.