First I wrote the C# code for a handler that captures the cache data and updates it in the DB if that cache already existed there. It works very much like the first UserScript, except that the first US asks “Do you want to upload the cache to the website?” when the cache does not exist in the DB, whereas the second one asks “Do you want to update the cache?” when the cache does exist in the DB. It just would not work, though, so I moved it to
localhost, and once it worked there, it was clear the bug had to be in the very first line, namely the one where I check whether the address contains geocaching.com/geocache/.
And sure enough, GC.com had changed the address back to the original geocaching.com/seek/cache_details.aspx? . So I changed the address in the US and suddenly it worked. To avoid being asked in chrome every time I open a cache page whether I want to update it, I keep this US in Chrome Canary, and whenever I want to update a cache, I load it in Chrome Canary, where I will not be browsing GC.com normally. For illustration, a few pictures:
The US asking whether I want to update the cache on the website.
The cache page on GC.com
My page after the update
My page before the update