RCH65

Still happens every single time. Looks like it tries navigating to N0° E0° in first place - which is exactly the shown 5320km from here...

There were no scripts running on my side... I even deactivated Tampermonkey to be sure... The problem comes... the problem goes... (and comes back again) without any changes (on my side). If European providers block geocaching.com traffic, you couldn't just switch between browsers - and the problems would occur all over the site I have the strong feeling that this is caused by some faulty data caching somewhere between 'you' and 'me' - and that the problem is somehow related to performance issues. This is why it comes and goes...

Here we go again... 😨 Now even one step earlier after clicking on 'view map' { "code": "CSS_CHUNK_LOAD_FAILED", "type": "error", "request": "https://www.geocaching.com/play/map/public/ActionBar.css" } { "componentStack": "\n at Lazy\n at Suspense\n at div\n at div\n at div\n at x (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:112440)\n at div\n at div\n at oe (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:91214)\n at C (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:195093)\n at s (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:81490)\n at O\n at u (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:402215)\n at L\n at t.SidebarProvider (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:10943)\n at M\n at t.ActiveCacheProvider (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:75249)\n at T\n at t.MobileListProvider (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:15962)\n at P\n at t.ActiveListProvider (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:77235)\n at D\n at t.ViewProvider (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:17699)\n at E\n at t.ApiProvider (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:18210)\n at A\n at s (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:80360)\n at x\n at t.MapProvider (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:78380)\n at F\n at t.BrowserProvider (https://www.geocaching.com/play/map/public/SearchMapDecorators.302c6cd0f4a07b726ddc.js:2:28034)\n at k\n at t (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:112036)\n at Suspense\n at t.TranslationProvider (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:784804)\n at n (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:422991)\n at t (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:114152)\n at t (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:108533)\n at l (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:353073)\n at o (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:354528)\n at C (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:195093)\n at f (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:193158)\n at C (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:735806)\n at div\n at i (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:1089861)\n at C (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:714332)\n at h\n at t.LimitSearchProvider (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:227307)\n at p\n at v (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:319697)\n at v\n at t.FiltersProvider (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:707983)\n at g\n at t.ExperienceProvider (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:706378)\n at m\n at t.UserProvider (https://www.geocaching.com/play/map/public/web-map.3.1.0.ffc2fa6443c5f75875a4.js:2:798898)" } Chrome 101.0.4951.67 (WIN 10) No scripts active. Works on Edge (same machine)

Strange... everything back to normal right now... Maybe it depends on to which server (instance) I am/was connecting to (?) Can't recreate the problem right now. Everything is fine.

Update: Both maps (search & browse) work on Microsoft Edge Cleared all related cookies in Chrome to remove old setting but no success. None of the maps work in Chrome

Have the same issue on Chrome 101.0.4951.67 (WIN 10) when clicking on a cache on the map: Tried switching over to 'browse geocaches' but the map there is completely messed up: Makes it very hard to plan our weekend... 😨

From time to time you have to empty the geocache_visits.txt file on your GPS device. The error occurs as soon as there are more than 1000 records in the text file. It looks like the process is uploading only new drafts (since the last upload) but this is not true. It's always uploading the entire file and the webservice throws away duplicate entries.

Check this thread:

Veeeeery annoying... Can't open links (even checkers) in a 2nd tab anymore by pressing CTRL

Ten years later... and we're still on GPX 1.0.1 without... - links to images - personal notes - "changed coordinates" indicator I know... the online API (available to handpicked developers) is sexy, cool and strategic... and downloading data (for undefined purpose to everyone!) is quite evil. It's still ridicoulously hard to perform a simple task like 'marking solved caches' on an offline GPSr without API access and 3rd party software. Believe me... there *are* reasons to use an offline GPS receiver. Why don't you give us the ability to write our own scripts by simply processing a GPX file? BTW: It's not *your* data... it's *our* data...

This is easy on the website: Just click on the 'pencil' (next to the solved coordinates in italic) and it will show the original coordinates.

Everything could have been so nice... An open Live API for everybody and evolving GPX versions containing even 'exotic data' like personal notes, links to images or Adventure Labs. Obviously, the fear of losing control over their (our!) data seems to be overwhelming. Otherwise, I can't explain, what they are (not) doing.

Es gibt ja noch eine weitere Umschaltmöglichkeit: Auf der (neuen) 'Search Geocaches' Seite ist rechts die Kartenauswahl mit den drei (nutzlosen) Karten: Geocaching, Google Road Map, Google Satellite. Das lässt sich wohl nicht ändern. Auf der 'Browse Geocaches' Seite kann ich rechts aus der ganzen Liste der (OSM-)Karten auswählen sofern ich links unter 'Set Map Preferences' die 'Leaflet' Auswahl getroffen habe. Sonst erscheinen auch dort nur die Google Map Optionen.

Even after 3 months, there are still bugs in the new search result function. When looking at a cacher's profile, the caches are being sorted by 'found date of the user' (latest on top), which is displayed in the 'Found On' column . So far, so good. This works correctly until 'dynamic data reload' is taking place (after 50 caches). From there, the 'Found On' column is showing the 'last found' date of the cache and not the found date of the user (anymore). Correct 'Found it' date above the red bar - incorrect 'Found it' date below red bar This was reported a few times shortly after the April release. If you can't fix this, you should bring back traditional paging. So called 'modern solutions' are useless, if they do not work properly...

Hallo Wolfsrudel1989 Das Forum ist natürlich nicht dazu da, um Mysteries zu lösen... andernfalls wären die Mysteries ja keine Mysteries mehr... Aber ja... das sind Daten, die ganz offensichtlich in hexadezimaler Darstellung aufgeführt werden. Falls Du vermutest, dass das (hexadezimal codierte) ASCII Daten sein könnten, würde ich mal eine Google Suche mit "HEX to ASCII" absetzen. Ich bin mir ziemlich sicher, dass Da *ganz oben* ein Link erscheint, bei dem man die HEX Daten reinkopieren kann und der dann die Daten in lesbare Zeichen umsetzt (sofern dies wirklich hexadezimal codierte ASCII Daten sein sollten)... ;-)

Any news on this matter? Talk to us!

Thank you for bringing back the 'correct' default sorting for viewing. However, there's still a bug when content is loaded dynamically while scrolling down. The sequence of the records seems to be correct (sorted by the *user's* "Found on" date when viewing someone else's finds) but the content is *not*. The "Found on" date of the user (green in the example snapshot) then changes to the (latest) "Found on" date *of the cache* (red in the example snapshot).

And be fixed so it still works after scrolling... (!!)

Why sorted from nearest to farthest? This only makes sense when searching for a particular location. Now, in most cases, you have to create the result list three times: - Default -> Nearest to farthest - Click on 'Found on' -> Oldest to newest - Another click on 'Found on' -> Newest to Oldest Poor hamsters...

Hmmm... strange things happen. It works! It *never* worked for me - not even once! And I tried many, many (many!) times. But now it does. Wow. I'm wondering what caused the difference. Hope this will last for a while... ?

There is a (undocumented? well hidden?) function when writing a log: Press '@' and you get a list of your friends to choose from. This is a very nice feature to mention somone, including a working link to his/her profile and an automatic 'Someone mentioned you...'-Mail to the referred profile. Nice! However, the function seems to be quite buggy. The popup list shows 10 (randomly selected?) friends. That's it. I'm pretty sure that - some time ago - it was possible to select additional/other friends by pressing the first letter of their profile name. This doesn't work anymore. The function only works once. If you press ESC, it won't popup again. Is this just me? Anyone else using this function? (BTW: Is this an officially supported function? Can't find any documentation...)

As far as I understand, you still may use PNG images - but not from Imgur (not allowed) and not from img.geocaching.com (automatic JPEG conversion). According to https://www.geocaching.com/help/index.php?pg=kb.chapter&id=97&pgid=956 you may use Dropbox or Google Drive to host your PNG image.

Yes. Definitely an incorrect configuration. Some of them just do not have HTTPS (geotrowel.me.uk in GC3AK1K). Others do have HTTPS but no own certificate (mattsphotobooks.com in GC7T963 is using the certificate of its hoster wpxhosting.com). There shouldn't be unsecured HTTP connections in 2020 and it's probably a good idea to move this stuff to the geocaching.com servers.

img.Groundspeak.com DOES support HTTPS - but is using a geocaching.com certificate. Just change the URL from http://img.Groundspeak.com/.. to https://img.geocaching.com/...