baracutio

As stated in the subject, all cache links in a trackable log history point to 'https://www.geocaching.com/geocache/GC0' instead of the correct gc code. Regards

No, it's the page with my own Adventure logs. -> https://labs.geocaching.com/logs

I analyzed the page load behaviour a bit. It seems like the page is loading all content up front. For me it results in ~450MB (of course, only pictures) to be transferred before I can use the page. Wouldn't it make sense to implement a simple loading="lazy" statement?

Here: https://labs.geocaching.com/logs

As stated in the title, I'm unable to delete my own Adventure Lab logs. Delete button appears, but nothing happens. Tested on newest Firefox as well as MS Edge. Regards

Since a few days I'm seeing randomly 'Error 500' pages when I'm... - opening single travel bug logs in a new page/tab - deleting travel bug logs - log travel bugs Reloading the page helps in most cases. Nevertheless, there might be an issue with the web services. Regards

Hey, I just noticed that the 'Log a geocache' page keeps loading something after I hit the send button. Cache is logged correctly, simply the page hangs. See screenshot for details. Regards

The point is, whenever I'm sending a message, I get an email. If I'm receiving a reply through message center, I'm getting no email notification.

Hey, I"ve just sent a message via GC message center to a colleague. Right after I clicked the 'send' button I received an email notification. The mail subject is saying 'Geocaching: baracutio, you have a new message from baracutio!'. Actually I'm not sending myself messages Here seems to be something wrong with the notifications. Greetings

Same for 'Archive' button as well...

https://www.geocaching.com/my/userrouteedit.aspx?rguid=9240af8e-f4d0-4ac3-951b-44591568edfb

Currently I'm building some PQs based on a previously created route - as many times before. The strange thing: When I'm increasing the search radius, the amount of caches along this route drops. Here's my comparison between search radius and amount of caches: 0.5km - 7 caches 1.0km - 13 caches 1.5km - 22 caches 2.0km - 31 caches 2.5km - 41 caches 3.0km - 58 caches 3.5km - 67 caches 4.0km - 77 caches 4.5km - 74 caches 5.0km - 55 caches 5.5km - 52 caches 6.0km - 49 caches 6.5km - 48 caches 7.0km - 48 caches 7.5km - 45 caches 8.0km - 38 caches 8.5km - 32 caches 9.0km - 30 caches 9.5km - 26 caches 10.0km - 26 caches Looks like at 4.0km radius is find the most. But why does the search results drop afterwards? Are there some server-side limitations that I'm not aware of? PQ settings: - route is 620km long - 1000 caches - cache types: virtual, earthcache - haven't found + is enabled - other settings are default Thanks for any help! Regards, baracutio

Same for me, log preview was quite nice. What is also really annoying: It is now too complicated to log 'needs maintenance' or 'needs archived'. Would be good to have this log types easier accessible (and better explained)!

Thanks for sharing your opinions! But how do you maintain your caches and check its logs? Or are you just 'accepting' every log? As stated in the guidelines... So, for me being a cache owner is more than just throwing lots of boxes into the woods. Everyone should be aware that maintaining and keeping a cache alive is additional work. I have seen a lot of good and bad examples in the past years. I think that not every CO is aware of its responsibilities and duties.

Hey folks, I haven't found anything regarding this topic, so I will start a new one. To keep it short: I would like to see a possibility for cache owners to mark log entries, which I checked online vs. physical logbook, as 'confirmed by cache owner'. Pros: - It adds an extra portion of quality and trust to the cache maintained by the owner. - It will add some credibility on user statistics. - COs who check their logs on a regular basis see at the first view, which logs are checked/to be checked (Think about holiday cachers: They're writing their online logs partially weeks/month after their visit). - It might reduce the amount of faked log entries. - Reviewers could see the activities and reliability of the cache owner. Cons: - Additional workload for the cache owner. - Instead of deleting logs, they will be just marked as 'not confirmed' or 'questionable log'. So, what do other cachers & COs think about this topic? Useful, unnecessary or nice feature? Best regards, Karsten

Thanks for your answer, but that is a just a workaround, which does not solve the problem at all. And, as stated in your post, I'm not the only one having this issue.

I'm having right now the problem that I logged some more (1000+) caches and I also logged 'took TB to GCxxxxx' for each of them. That will generate a lot of list entries on /my/default.aspx site in the section 'Your Logs (Last 30 Days)'. In numbers: We're talking about 9.500 list entries! It takes forever for the browser to download and render the content. Tested it with Firefox 47.0.1, IE 11 and MS Edge browser - site becomes unusable till the whole website content is loaded. I can also imagine that it is an unnecessary load for the webservers, too. So, might it be possible to limit the list entries to a ) the last 30 days and b ) to a maximum of 500 (or maybe 1000) entries?

Yesterday I logged them with an older date because I found them last month

http://www.feuerwehr-grambin.de/assets/gc.png As you can see in this screenshot, first came all the caches, second the TBs. BR

The problem with the wrong date is solved. Thank you so far! Additionally I found a small cosmetic issue. After I logged three caches I noticed that the log history is ordered in a wrong way. Normally it should show logs in this order: cache, TB, TB, TB, cache, TB, TB, TB and so on. But now it is like cache, cache, cache, TB, TB, TB, TB, TB, TB etc. Could you please fix it also? BR, Karsten

Hey! I'd like to report a bug concerning the log date of cache & visited TBs. Example I log a cache and set the found date back to e.g. 25th October. For my TBs I click on 'all visited'. Normally the date for both logs (cache & TB) should now be the 25th October. Error Since today (or yesterday?) the log dates are totally different. The cache log date itself is correct (e.g. 25th October), but visit logs for TBs are all logged with 'today'. Would be nice to have it fixed BR, baracutio