theflights

This is a expected, as mapping caches that are found by other players is not possible. Why is it not possible to map caches found by others? Is it a privacy thing? If so, would it be possible to consider allowing us to map caches found by people in our 'friends' group?

Thanks for your reply. That's a shame if that's the case. Three of us regularly go out together but when one isn't available we try to do caches they have already done, keeping ones we all haven't done to do together.

Does anyone else have a similar problem to this?... 1. When clicking on filters in the 'Search Geocaches' map page there is no option to search by 'Found by'. That option is present when searching via 'Play' and 'Search' and clicking on filters. 2. When going to 'Search' via the 'Play' menu, then clicking on filters to search using 'Found by', the list then appears as normal. However, the 'map these geocaches' option, normally on the left above the list, is not there, neither is the 'Add to List' option. These options are there on any search I've tried not using the 'Found by' feature.

Although I have had no update from Groundspeak on the ticket I raised with them back in May, it does seem that this issue has been resolved with the latest update to the search facility.

I haven't heard anything from Groundspeak since I highlighted this post to them in May as part of my open ticket. I have been using the workaround. However, the workaround seems to have failed now too. I searched tonight, using the 'filters' on the map page. The URL keeps the capital letter in the username but it is not filtering out finds for the user.

Yes, I agree with you on that. I currently have an open ticket with Groundspeak and have linked this thread to the ticket. I have been assured it will be dealt with but was given no timescale.

Thank you very much for your work and reply. I can confirm that carrying out the 'adjustment' to the filters on the map page and clicking done, but changing nothing does give the correct result. Thanks for pointing that out and I will be able to use that workaround until Groundspeak get to the bottom of the problem.

Thank you very much for taking the time to do the research and report back. I hope Groundspeak are able to resolve this issue soon as it clearly affects other users and not just me.

That is very interesting. Can you narrow it down to searching for NFB for a user with at least one capital letter in their name? I did have problems last year whereby I would type a username and I basically got a white dropdown box with no user avatars. I presumed it was a glitch as it did rectify after a few weeks but I'm now starting to wonder if that was the beginning of my problems.

I noticed that too. I did capitalise it but it immediately goes back to lowercase. The G is also not capitalised in the search carried out by a friend (second image) and that one shows the correct results.

Thank you very much, I pleased it's not just me! I will wait and see if anyone else has the issue too and then report the findings back to Groundspeak. Hopefully, they will get to the bottom of it and resolve it.

I will try. When using the search filter to show caches 'not found by' any user with a capital letter in their name, the initial list of results comes up as correct. Then, when I click on 'Map these Geocaches' the results are incorrect and will show geocaches that user has already found, thus not filtering any of the finds out. I have attached an image, with permission of the user concerned, Goldfish58. The arrows shown indicate two caches I know that Goldfish58 has already found. The URL is shown in the picture, shows we should be looking at 'NFB' caches. The second image is exactly the same search carried out by a friend and shows the correct results.

We have a problem with the premium member filtered search facility, specifically when using the 'not found by' field. This problem has been going on for at least a year now and, now we have more freedom, it is now really causing us issues when trying to meet up with friends to geocache. We have tried numerous scenarios on two different computers and three different browsers. One browser was a virgin installation which had never been used for anything else. When searching using 'not found by' for a lowercase username there is no problem at all - all results are correct. However, if carrying out an identical search but for a user with at least one capital letter in their name, the results are wrong. The results appear to ignore that user on the map. The results in the search list are correct, but they do not translate over to the map. However, friends (both with uppercase in their name and all lowercase) can carry out exactly the same searches without a problem, therefore the issue appears to be with our account rather than computer related or across the board. We have been in touch with Groundspeak and, as far as they are aware, nobody else has the same problem and they can't recreate it. They have asked us to post here to see if anyone else has the issue which, hopefully, will enable them to do more research and see if they can get to the bottom of the problem. Please let us know if you have the same problem or have had the same issue and know how to resolve it. Many thanks