Jump to content


+Premium Members
  • Posts

  • Joined

  • Last visited

Everything posted by LivingInNarnia

  1. @JuRoot thanks for your feedback. You are correct, as part of the edit cache page listing release we removed the addition of the lookup code. The lookup code was actually not being used - it was added years ago as a potential use for saving to a GPS, but it was never implemented. The Prefix Code is what is currently used in GPS devices to identify stages and that will continue to remain as part of waypoints. Currently we continue to display the lookup code on the Cache Details page but we don't allow editing. We will be removing the lookup code entirely sometime soon, it's already not being displayed in our apps. Thank you!
  2. Thanks for sharing your concerns - we're not ignoring you! To update the fake coordinates for you mystery cache to align with the guidelines, there are 2 solutions outlined here in the Help Center. As your posted coordinates are more than 528ft from your Final, we would recommend contacting a reviewer as you have done. As you know the reviewers are volunteers and I would imagine with the holidays it may take some time to receive a reply. There is additional information about the other volunteers available in your area in the regional wiki, reaching out to another reviewer may be an option for you.
  3. If you would like to make edits to those caches, you can move your fake coordinates so that they are within the 2 mile limit. You can see earlier comments about this in this thread here and here. Thank you!
  4. This is a known bug and the development team is working on getting this resolved - we hope to have a fix out for this very soon! Thank you for reporting.
  5. Hello! Would you mind sharing the GC code of the cache you are having the issue with? Also the browser you are using (Chrome, FireFox etc). We'll see if we can reproduce the issue on our end. Thank you!
  6. We're working on resolving a bug that caused some users to have issues saving/editing waypoints and viewing the map on the new edit page. This fix should be pushed out today, thank you to those of you who reported issues. UPDATE: this bug is squashed
  7. We had a lot of conversations with the volunteer reviewer community and the community about these changes. The 2 mile rule for mysteries has been in place for some time and the volunteer reviewers have had the task of reminding COs to follow the guidelines. Now that Geocaching HQ enforces the 2 mile rule on the Edit Page, the volunteer reviewers have fewer errors to chase after and to ask the cache owner to update.
  8. Thanks for the question. The 2 mile rule has been part of our guidelines for some time, and we are enforcing the rule (along with others) as part of the changes to the edit page. As you mention, I would recommend changing your posted coordinates so that your cache aligns with the guidelines for mystery caches outlined here: https://www.geocaching.com/help/index.php?pg=kb.chapter&id=127&pgid=277
  9. Thank you for reporting this issue! Could you let me know which cache you are looking at and which browser versions you are using so that we can try to reproduce the issues on our end? Much appreciated, we'll do our best to get this resolved quickly.
  10. Hello! In this release we also updated the cache state messaging which you notice in the blue box - for example locked, disable, or archived caches. The old red text was hard to read and sometimes confusing - the updates bring it in line with how we are messaging on the website. Thanks for sharing your feedback!
  11. We've been working on a fix for this bug and we'll have the update in production in the next few hours! The issue was a data anomaly in NZ - thanks for reporting the issue here.
  12. along with the link to the Help Center update, the input will not be case sensitive and we'll be more forgiving with spaces too!
  13. This sounds like a bug! Could you let me know which cache you are having the issue with? A GC code or URL would be great. Thanks!
  14. Thanks for the feedback - we're adding in a link to help explain this a bit better. In the meantime, you can see more information about coordinate formatting in this Help Center article: https://www.geocaching.com/help/index.php?pg=kb.chapter&id=128&pgid=811
  15. Thanks for the feedback, we'll take this into consideration as we make updates/fixes to the page.
  16. In this release we also updated the cache state messaging which you notice in the blue box - for example locked, disable, or archived caches. The old red text was hard to read and sometimes confusing - the updates bring it in line with how we are messaging on the website.
  17. We are aware of this bug and we are looking into it! Thank you for reporting here. UPDATE: this bug is fixed.
  18. Tooltips should be there! Is there a specific attribute for which you are not seeing the tooltip?
  19. Thanks for the feedback! Glad you like the changes Regarding wheelchair attributes: the attribute is only required for T1. A cache could potentially be wheelchair accessible at a higher terrain rating and that is up to the CO and reviewer to discuss if needed. See the guidelines here for more info: https://www.geocaching.com/help/index.php?pg=kb.chapter&id=97&pgid=82 Thanks for pointing out that edge case. Regarding sizes, both the milliliter/liter and the more descriptive sizing are used in the Help Center article you referenced. We are using the the descriptive sizing to provide people with a visual, a little easier to understand. The size descriptions are meant to be a guide, we will look into adding more visual language to help with that.
  20. Thanks for the feedback! Looks like there's a small caching issue with the solution checker (if you refresh the page you should see the solution checker display on the cache details page). We'll get it working so that it shows without needing to refresh.
  21. Thank you! The Related Web Page option was removed from the Cache Submission Process a few years ago. And now, it is removed from future listings (only old listings that already had that field filled out will show up). The cartridge link and information related to puzzles should be provided in the description. (It should also be noted that the related web page is already not displayed in the mobile app).
  22. Thanks for letting us know - I've notified our engineering team and we'll work on getting this bug fixed. Thank you!
  23. Loading issues should be resolved now for all browsers - please let us know if you continue to have issues, thanks!
  24. Thanks for reporting the issue. We're aware of the problem and are working now on resolving it - you can see additional updates and info in this forum thread:
  • Create New...