Keystone

I reviewed the cache page that gave rise to this thread. In Reviewer Notes posted to the cache page, the OP states that they are 15 years old. A cache can be hidden by someone who is underage, provided that their account is supervised by an adult. But, a geocacher must be at least 18 years old to post in the Geocaching Forums. For this reason, I am closing this thread.

There are legitimate reasons for this, such as: The cache owner hides a large number of caches along a trail, submitting a few each day as they have time to do the writeups. Once published, the CO edits all the cache pages to make the hidden date uniform for their series. A hider really really wants to own a cache hidden on February 29th. Being a good hider, they submit the cache page for review on February 22nd, asking their Reviewer to publish it on the 29th. After the review process is finished, the Reviewer locks the cache page until publishing it on the 29th. After publication, the hider changes the hidden date to the coveted leap day.

I moved this topic from the Geocaching Apps forum.

Using an automated process, Geocaching HQ archives all regular events and CITO events four weeks after the event date. As a reviewer, I don't miss doing that manually! Keeping the event cache page active during that four week period can be helpful for attendees who haven't logged yet, didn't save a draft log, and might have trouble locating the cache page for a temporarily disabled event.

I'm closing this duplicate thread.

If you're a GSAK user, see the discussion beginning here in a thread from last month.

I moved this thread from the "How do I...?" forum, since it is more of a feature request.

A challenge cache like the 2013 cache linked in the opening post wouldn't be published today. Even if the challenge cache rules allowed for user-defined polygons, how would the borders be drawn? Assume that there's a guardrail cache in a car park across the street from a world heritage site, and there's a four-stage multicache that begins three miles away from the world heritage site, but includes two stages at that site. Which one counts for the souvenir? Now, repeat this subjective judgment for every other World Heritage Site.

I see that your account doesn't own any caches. What cache page are you trying to update?

I'm closing this duplicate thread because the OP has also bumped the active thread. Also, the post is disrespectful both to Geocaching HQ and to fellow geocachers. Don't report bugs this way.

I moved this thread from the General geocaching topics forum, where the prevailing language is English.

I moved this thread from the "How do I...?" forum section, where the prevailing language is English.

There has been no rule changes on this topic; perhaps that's the source of your angst. There have been some new attributes introduced, such as Bonus Cache Attribute and Challenge Cache Attribute. But, they merely enhanced an existing framework - they didn't change it. The Letterbox Hybrid guidance from Geocaching HQ has also been consistent for many years. As has been noted above, if the concept of attributes had been around at the time when Jeremy Irish identified a need for a way to alert finders not to steal letterboxing stamps, then "Has a Letterboxing Stamp" would have been an attribute, not a cache type.

There's a D/T History feature available to paying members of project-gc.com. Using that tool, I see that 143 of your finds have had their D/T rating changed since the date of your find.

This can be done in bulk using the API. Once you have a filter of all the caches you don't want, go to "List Manager" under GSAK's "Geocaching.com Access" menu. Select your Ignore list, then choose Add Caches to List and specify all the caches in your filter.

You don’t need to worry. West Virginia cache submissions are capably handled by two dedicated volunteers. If they ever got too busy, there are backups in place. Based on current new cache volumes, that’s not a concern.

After seeing your report, I've just updated a half dozen pocket queries, and created some new pocket queries, across two different browsers (latest versions of Edge and Firefox) and using two different accounts. I did not see any Error 500 messages. What browser(s) and operating system are you using? Is the behavior persistent or sporadic?

I moved this thread from the General Geocaching Topics forum section.

There's no such thing as "deleting" a cache page from the database. Available options include: Archive the cache page you don't need. Recycle the cache page later on, for use the next time you want to hide a cache. Keep it disabled in the meantime. Adopt the page over to a separate account prior to archiving it - which is a bit of work, but keeps your list of caches clean if that's important to you.

And I moved your post over to this thread, where it's on topic.

I moved this topic of local interest from the General Geocaching Topics forum section.

I moved this thread from the General Geocaching Topics forum, where the prevailing language is English. I can confirm that Cuba has had a country souvenir since 2019.

The sole distinguishing feature of a Letterbox Hybrid cache is the presence of a letterboxing stamp. Otherwise, the cache takes on the character of, and is subject to all the listing guidelines applicable to, the underlying cache type. Find a container at the posted coordinates and sign the log: Traditional. Add a stamp: Letterbox Hybrid. Find something at the posted coordinates that directs you to another location, and eventually a container and log: Multi-Cache. Add a stamp: Letterbox Hybrid. Solve a puzzle or do something else to find out where to go first: Mystery Cache. Add a stamp: Letterbox Hybrid.

The final stage of this multi-cache doesn't meet the Geocache Hiding Guidelines, and should be modified. The concept that the logbook must be enclosed within a separate container has been a requirement that Community Volunteer Reviewers have been directed by Geocaching HQ to enforce since July 10, 2007. (I'm staring at that directive in another browser tab, and it's crystal-clear.) Reviewers do not "approve" geocaches or their designs. We publish caches that appear to meet all of the Geocache Hiding Guidelines, and based on what's told (and not told) to us during the review process. In the first instance, it's up to the cache owner to be familiar with those guidelines and submit caches that comply with them. Publication by the Reviewer is not a guarantee that all Guidelines have been met. Reviewers don't delay publication to play "Twenty Questions" and obtain explicit answers for any possible Guideline issue -- "Prove to me that no digging is required, either to hide or find the container." "Prove to me that the original cache contents do not include any prohibited items." "Prove to me that the cache includes both a container and a log." Etc. etc. etc.

The website seems to be working again. As this was a poorly written bug report, I'm locking the thread.