Keystone

Please see this Help Center article. Note that it doesn't distinguish about cache page log types. A prior version of this article said that only "Found it" logs (or equivalent) would be restored by HQ where appropriate. That language is no longer there, so it appears possible to appeal the deletion of a DNF log to Geocaching HQ. I know from past experience with my player account that HQ will restore DNF logs when appropriate, but that happened for me back in 2009, when the Help Center was just a twinkle in Signal the Frog's eye.

You can write to the logger and ask them to edit their log. If they refuse or take no action within a reasonable time, you can delete the log. But, this sometimes triggers a back-and-forth contest, ending in someone reaching out to Geocaching HQ to act as a referee in a logging dispute. That's time consuming, and not much fun. So, a further alternative is to post a note as the cache owner, explaining in a fact-based way why the information in the log is inaccurate, misleading and potentially harmful. If the logger responds by posting a rebuttal note, you can safely delete that. They're entitled to a DNF log, but they're not entitled to turn your cache page into a discussion forum.

Besides DNF logs not being allowed as part of a challenge cache's requirement, this would be an unacceptable date restriction. Challenge caches should be available for anyone to find, provided they meet the requirements. A person who discovers the sport for the first time and signs up for a geocaching account on the day after this challenge cache is published could not, by definition, log a legitimate DNF log on a date prior to challenge publication.

While Virtual Caches can now be adopted -- a relatively recent change -- the time to arrange for this would have been prior to archival. Once a cache is archived, it cannot be unarchived for the purpose of facilitating an adoption.

I moved this thread from the "How do I...." forum section, which is for questions about Geocaching.com website functionality, typically posted in the English language.

This forum section is for bug reports and feature requests for the official Geocaching smartphone apps. Since the OP is using a GPS, not an app, I am closing this thread in favor of the existing discussion in the Geocaching.com website bug reporting and feature request forum. I see that the OP is already active in that discussion.

Read my posts from earlier in this thread.

I looked at your cache page. The design is far more complex than what you've asked in your opening post. Discussion participants are cautioned accordingly.

You can figure out the answer by reading this page.

I merged together two threads about the same subject.

If you're trying to exclude owners who have hidden caches, a filter based on "not found by" won't help at all. A cache owner cannot find their own cache, so nothing will be filtered out. What's missing in the search filters is the equivalent for "Hidden by." There is a filter to return all caches hidden by a specified cache owner, but there is no filter like "Not Hidden by." The only available site functionality is to put caches by these cache owners onto your "Ignore" list. That must be done one cache at a time. There is no "bulk ignore" for all caches hidden by a particular geocacher. This is a feature that's been requested over the years. What you're attempting to do is quite easily accomplished using third party tools. For example, could you let us know if you are a GSAK user, or if you use a smartphone app from an authorized third party API partner, such as Cachly?

Allow extra time for everything on the site to synch up when you modify past log history.

There you have it. Allow extra time for everything on the site to synch up when you modify past log history. In any event, this thread is about Adventure Lab finds and deletions. I now return everyone to our regularly scheduled topic.

This is the correct forum section for reporting possible website bugs, and you've made a good report. You could add to your report by saying what operating system and browser versions you are using when experiencing the errors. You can also write to Geocaching HQ via the Help Center to report a bug. Use item 18, "Bug reporting," from the dropdown list where you're asked how to categorize your request, so that your inquiry routes to the correct team.

I'm locking this thread, because this forum shouldn't be used as support for unauthorized third party applications. Feel free to discuss the official Geocaching applications, as well as authorized third party API applications.

But you did receive a specific note on December 5, reminding you to Enable your cache page. You made a mistake by just writing a note when you replaced your cache on November 27th. I found it courteous that your Reviewer explained the correct process. You then made a second mistake by ignoring the Reviewer notes, leading to the archival of your cache on January 4th (four weeks after the reminder note). If you are not checking your emails, that's on you. The instruction to use a "Write Note" log only applied if you were planning to replace the cache, but could not yet do that. When you do replace a cache so that it's ready to be found again, the correct log type is "Enable."

A cache in a Disabled or Archived state would not cause the error 500.

Yes, "spoiler sites" are very much a thing, both as standalone websites and social media channels. The log photos that you posted looked dry, neat and easily verifiable by a cache owner. If you found one that was unsignable, wet and falling apart, you can log "Owner Attention Requested."

Yes, the circular link is a valid bug - it should take the user to the Help Center article.

Sometimes it takes a few days for the account/dashboard pages to catch up with the most recent information on a cache page.

If you want your Reviewer to check coordinates more than .1 miles away, write an email via their profile page. That workflow is an exception, and is not readily susceptible to automation.

The sole distinguishing feature of a Letterbox Hybrid cache is the presence of a letterboxing stamp. If you want to give away non-commercial stickers in your cache, that's fine, but this would be a different cache type, depending on the design.

Discussion in this thread should be limited to the bugs about links between trackables and cache pages. Other unrelated bugs should be discussed in separate threads for those bugs. Thanks.

I moved this Adventures-related question from the "How do I...." forum section.

This is up to the owner of the Virtual Reward Cache. From the perspective of Geocaching HQ (log dispute resolution) and Community Volunteer Reviewers (cache page guidelines compliance), all that matters is whether the finder can meet any permissible photo requirements and provide the right answers to any verification questions. So, if the photo requirement is to post a picture of a famous landmark, and a geocacher has one from years ago because everyone who visits this landmark takes a photo of it, this can qualify if there are no additional conditions. Virtual Reward Cache Owners who do not want to allow previous visits can add guideline-compliant conditions, like requiring a photo that shows not just the famous landmark, but also a sign with their caching nickname and the current date. A verification question that asks for a trivial detail can also protect against logs based on prior visits. I might have a picture of Niagara Falls taken from a certain popular spot, but I'm unlikely to know the text of Rule 7 that's posted on a nearby sign which lists the ten rules that visitors must follow when they're at this location.