Sandy

These discussions might get more traction if posted in one of these sub-forums: Regions/States

These discussions might get more traction if posted in one of these sub-forums: Regions/States

A gentle reminder to please be respectful of each other in the Geocaching.com forums as per our guidelines. Thanking you.

Everybody is reminded to adhere to the forum guidelines, please. Some posts in this thread are bumping up against it. Thank you.

The tone of this thread is degenerating. This is not helpful - or respectful - commentary. We are aware of the inconsistency and what is required to address it. And the Block Party may not be of interest to you, but there is no need to frown about it. Color inside the lines, please.

Are you logging in through iOS? And if so, have you turned off 'private browsing'? If not, then we will inform the engineers who are still investigating the lingering issues. Thank you. Thanks for the update.

Are you logging in through iOS? And if so, have you turned off 'private browsing'? If not, then we will inform the engineers who are still investigating the lingering issues. Thank you.

Update: The issue for the majority of geocachers unable to log in was recently fixed. There are, however, some lingering problems that we are currently investigating. We apologize to those who are still affected by this issue, but think that this may be due to a password update. If you have recently updated your password, we asked that you attempt logging in after one or two hours post-password update. The issues some geocachers are having with iOS log in appears to be corrected when you turn off "Private browsing" in their Safari settings. We will continue to monitor this thread.

content by adamstuart07 removed. contacting user.

has been sold. closing.

This is very sad news.We send our condolences to his family, fiance and friends.

We will investigate further.

This discussion has digressed several times, which multiple posts being reported by forum participants. Closing this thread with the reminder to all participants that the forum guidelines apply to all posts and all participants.

Mega-Events Article updated to include (new) benefits .

After today’s release we experienced some unexpected issues and as a result, we have rolled back this release. We are working to correct these issues to ensure the quality of your experience. We will provide more information as it becomes available.

We hope so. If not, please report the issue to us and we will pursue further investigation.

This issue has been resolved. Thank you for your patience.

If you logged a cache since the issue began, expecting a souvenir that has not appeared on your profile page, please email us at contact@Groundspeak.com with the GC code of the cache (or one GC code, if there were multiple caches for the same location) and the souvenir you expected to see on your profile page. We will update your profile for you.

Does this problem persist?

We apologize for the bug that has affected the font in this forum thread. It has been reported to Engineering, but we do not anticipate a fast fix.

Hello cache owners. As you likely know we have a team of highly-experienced and dedicated volunteer reviewers who review each cache page that is submitted to Geocaching.com, to ensure that it meets guidelines and is publishable on our site. The local reviewer typically begins the review process within 3 days of when a new listing is enabled by the cache owner. In the high season, which begins in (northern) Spring and extends through to the end of Summer, this expectation can be more difficult to meet. Understandably, when the weather is finer, the volume of caches submitted to the reviewer team increases significantly. For this reason, during the high season we will be extending the time to begin the review process to seven days. We will hope to get to each listing before the 7-day time-frame, but we thank you for your patience in advance.

Updated event cache guidelines affect cache events, CITOs and MEGAs, regarding sponsorship. http://support.Groundspeak.com//index.php?pg=kb.page&id=308

We believe we have now fixed this issue. If the issue recurs, please email contact@Groundspeak.com.

Some users are getting a "Password incorrect" error message when attempting to log in. Our Engineers are working to identify the cause of this issue. If occurs/has occurred, here is some important information for you: The bug is being misidentified by our system. It is not a password error. Please do not update your password. Please try logging in at another time. If possible, use the cached password stored by your browser, rather than typing the password manually. If you have already linked your account to log in through Facebook, please do so, as this log-in process seems to be working. We will update this thread and our site status page when we have resolved the issue.

I'm confused. So has this cache been rejected by appeals, decision final? Correct. This was explained to the cache owner via email prior to us posting in this thread.