richlv

Support was a bit confused about error 500, but a bit later it started working - I guess developers got information about the errors from the logs

Thanks, as the error still persists, submitted it in the help center.

Still getting error 500 (for the record, that should never happen, it's "Internal Server Error"). Is there any better way to report bugs like this?

Indeed, nothing should cause 500 - it's always some error on the server side. I still cannot log a find on https://www.geocaching.com/geocache/GC8ZKF7, error 500.

And now cannot log a find, error 500 again. Any guess when this could be fully solved?

For the record - worked now.

Attempting to log an earlier DNF on https://www.geocaching.com/geocache/GC7T8JA fails: Browser gets error 500: Is this a known issue?

You might want to use a feature like Firefox containers - use a different container for different users. That way cookies are not mixed between sessions. What you are likely doing is logging everything in your name, if that is a single browser session.

Thanks, does this mean there could be a fix soon?

I always used the "old" logging form, and it nicely preserved the previously selected date (until day change in the USA, I believe). It looks like the "old" form has been removed now (don't see the opt out link anymore), and I'm stuck with the new form, which does not preserve the date. Can we please get the old form back? It worked better

"You've found too many caches" could be used in other contexts, too

Excellent - copy-paste gets a TSV, which is parse-able. Thank you so much

Thanks, that falls under the non-free options, unfortunately

There are multiple forum topics about seeing a list of found caches in the webpage. I'd like to get a list of all my found caches - primarily interested in the GC codes, and would be happy with a plaintext, CSV or similar file. Can I get something like that as a download, from API or in a similar manner? Preferably simple (to avoid website scraping) and without extra expenses.

I sure did - it did not work back then. Works for me again now. Did not record what was the URL it used that failed before, unfortunately cannot compare to what it's using now.

Looks like the site has changed and the logging from GC admin page does not work anymore. Manually constructing a link like https://www.geocaching.com/play/geocache/<CACHEID>/log still works.

After logging a find, "View Geocache Log" page is opened. The editing icon (with a pencil) does not work as expected, though - it tries to add a new log instead.

Seeing the same problem with Firefox. Shift+Enter does not work. Pasting some text with a newline in it can rasult in the unfinished message being posted 3 times in a row.

In an older version of Firefox, the new map (/play/map) is a blank page. Not sure whether related, but console shows: mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create mapbox-gl.js:29:6520 SyntaxError: let is a reserved identifier vendor.c8643ec5d6d1f0f96541.js:2:603822 The "old" map (/map) works.

Never received those. After how many consecutive DNFs do you get them?

I like older caches. I also try to help with the maintenance of them, and with as god container as I possibly can. While I can see the argument of drop-and-forget caches seeming to be encouraged, in most cases it's a good reason why the owner might be unable to do so - it's often moving away, health issues or death (yes, GC has been around enough for many members to have... expired). I like those caches because I see the opposite - drop-forget-drop-a-new-one - as a much bigger issue. There are some prolific cache authors who, while their efforts are appreciated, do not seem to care for the longevity of their caches at all. You can find cache comments like "oh, archiving this one so I can hide a new one at this same place so my friends can get a new find". Wat? Old caches are great and highlighting them would be nice. Perhaps the opposite is needed, too. GC recently offered a chance to place new virtual caches to cache owners whose caches had many favourites (or something, the criteria was secret). That seemed like a great idea to discourage the "cache droppers". Perhaps something opposite could happen to cache "unmaintainers" - if many of your caches get disabled/archived, you don't get to hide new ones, or your find number is halved, or something

could be related to switching to a new map style/tiles : https://forums.geocaching.com/GC/index.php?/topic/345928-missing-some-ponds-on-geocaching-map-layer/

GC map is all grey, was OK a few hours ago. Is there some maintenance, or a known technical issue ?

MartyBartfast, thank you - i had indeed overlooked that option and it solves the biggest issue. still, as cezanne notes, cache pages (and trackable map, although that one is less of an issue) is google maps now - and i'm fairly surprised by how much better osm is...

well, with the latest changes on geocaching, the useful osm map is replaced by... quite less useful google map. anybody got a snippet that would provide osm for the gc map view ?