Muddy Woodies

I've had the same issue for some time now - all our pocket queries will not show the correct map, just the standard one (as in 'Play' > View Browse Map), centred on our home location. As such, for months now, I've been effectively working blind and have to guess the extents to which a query centred a location, will run to. Using Microsoft Edge and Windows 10 (Windows 11 not an option without a new PC, thanks to Microsoft)

I have just replaced and enabled a cache while at GZ, using the Geocaching app (iOS) and received e-mail confirmation a few seconds later, however the app continued to show the cache to be disabled. Well over two hours after enabling the cache, viewing the listing (accessed from the app, via list or map) still shows the cache to be disabled, even though ‘Activity’ shows that it has been enabled (I've also noticed that the last activity (shown on the opening screen for a cache), doesn't refresh until it is selected, going back then indicates the true latest activity). Presumably, at some point the status of the cache will be refreshed on the app??? However, I'm unsure as to whether other iOS app users will yet be able to see the cache - there doesn't even seem to be an option in 'Filters' to make other owner's disabled caches visible (I think there used to be?) - they're effectively non-existent on the app. Shutting down the app and reopening has no effect. The website is fine and shows that the cache is enabled, third party app ‘Cachly’ also gave the correct status, within seconds of doing the maintenance. Is this a bug, or just the way the system driving the app refreshes?

Just had the same issue here - have replaced a temporary container with one similar to the original and needed to revert the hint. Will add a note to the maintenance log and edit the cache listing when the bug's been fixed. Many thanks for actioning.

Have found that the issue seems to be fixed by clearing cookies from geocaching.com within Chrome settings> Security and Privacy>All Cookies and site data Sorted for me, hope this is of help!

Same issue here in the UK with Chrome, also continues after I updated to Version 97.0.4692.71 (Official Build) (64-bit). However, Edge [Version 97.0.1072.55 (Official build) (64-bit)] is working without issues at present. Lists are also not working from Chrome Dashboard (does nothing at all), but they can still be accessed from Geocaching start page, or the old dashboard, which appears to be working fine within Chrome. Using Windows 10 Pro, build 19043.1415

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......

Thanks very much, that's great - I knew it would be hidden away somewhere. Will be able stick with the new page all the time now - the activity display on owned caches, in particular, is very useful.

How do I edit our profile from the new profile dashboard? At present, I'm going back to the old page and clicking on 'Edit Profile', I can't find it on the new.

We have completed work on a fix for this bug. It should be released next week. Thanks for the quick reply, we look forward to the fix!

After 'Search for nearby caches' and 'Map these results', only the caches within a 10 mile radius are shown. I hit the 'Clear Search Filters' button to expand the displayed caches in Chrome. However, when clicking the 'Clear Search Filters' button in Internet Explorer, '404 - file not found' is shown. It still appears to work fine in Chrome. I have needed to migrate to IE from Chrome, so that 'Upload to GPS' (Garmin) works, as the plug-in isn't supported by the current and future Chrome releases. Current situation is somewhat limiting - without a search relocation or change of defaults, I can't be selective on the map display or easily upload individual caches which are more than 10 miles away.