Keystone

Closing duplicate thread. If you have further questions, @yxza, please post in the active thread.

I am closing this duplicate thread.

You don't understand. The cache in question was published in 2011. The guidance you're quoting didn't exist then. Internal guidance to Reviewers matured on this subject in 2014. Think of caches like this one as the reason why the current guidance is stricter. Legacy caches like the one discussed in this thread met the guidance in effect when they were published, so they're allowed to continue.

I moved this thread from the General Geocaching Topics forum.

I recommend contacting the EarthCache reviewer for your area, GeoawareUSA10, by email through his profile page. GeoawareUSA10 covers all the states near your home (PA, OH, KY, WV, MD, NY, etc.). If your ideas come from more distant travels, let us know where. If you stray much further south (Virginia, Tennessee, etc.) you would switch over to geoawareUSA9. Both of them have handy maps on their profile page to show how coverage for the USA is split up. Many Reviewers, including myself, do not use the message center for "official business," but others do. It's always a safe bet to start your contact with an email through Geocaching.com, and then ask later if the message center is OK. Don't be surprised if you're asked to write up a draft cache page with all the details. Email is fine for general questions, but at some point the geoaware will want to see the exact text for the background information and verification activities/questions.

It's an irrelevant question, because the OP must certainly have permission from the land manager in order to have their cache published as an exception to the Geocache Hiding Guidelines. I appreciate the OP's question, which demonstrates they've read the following guideline text:

Challenge Caches published before April 21, 2015 are considered "legacy caches." For those older Challenge Caches, the finder needs to comply with the logging requirements specified on the cache page. Some owners of legacy caches have opted to update the logging requirements to rely on a checker. Others have not. Even if a checker is available for a legacy cache, the requirements on the cache page control.

Based on the quality of your first post, I can only say: please post more often!

Please see this active thread in the Website Bug Reporting and Feature Suggestion forum. Geocaching HQ has acknowledged the issue. I'm closing this duplicate thread.

I am closing this duplicate thread. I will note that the removal of the "audit log" was for privacy law reasons. This was an intended and announced change.

I am closing this duplicate thread.

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

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.