+A J Pombo Posted March 13, 2022 Share Posted March 13, 2022 When i try to edit an old cache the site show me an error message: "The date must be within the last year"" I get this error in my caches (all old caches) Anyone have the same problem? Quote Link to comment
+Hofstad Posted March 13, 2022 Share Posted March 13, 2022 Came across something that seems to be a bug when editing a cache description on one of my older geocaches. After making my changes, the edit form won't save, giving an error message in red by the 'Date Placed' field: The date must be within the last year. The geocache in question was originally hidden in March 2014, and the form did save when changing the date to a more recent one. I expect this to be a bug, as this requirement would make more sense with new cache listings and shouldn't apply to editing existing caches. 2 2 Quote Link to comment
+Radler Posted March 13, 2022 Share Posted March 13, 2022 I do have the same problem. This is quite annoying. I made many changes, because the forest has changed again and I need to move stages, change descriptions etc. Now I can not save my many changes. Quite annoying for somebody trying to be a good maintainer. 3 Quote Link to comment
Frau Potter Posted March 13, 2022 Share Posted March 13, 2022 Thank you for reporting this issue. We agree that there is a bug and users will be unable to edit older cache pages until we get this fixed. We will notify the engineers and hope for a fix early on Monday. We apologize for the inconvenience. 1 2 Quote Link to comment
+Jayeffel Posted March 13, 2022 Share Posted March 13, 2022 Maybe in the meantime Write a Note log with the information you desire Quote Link to comment
Frau Potter Posted March 13, 2022 Share Posted March 13, 2022 Yes, we can confirm that we have a bug. We will notify the engineers. In the meantime, we recommend posting a Write Note (log) on the page, to let geocachers know about the change that you plan to make. We apologize for the inconvenience. 1 2 Quote Link to comment
+Hofstad Posted March 13, 2022 Share Posted March 13, 2022 Thanks for your response! Added some information to the cache page notifying visitors about the erroneous date. Quote Link to comment
+baer2006 Posted March 13, 2022 Share Posted March 13, 2022 Just wanted to report the same bug. Super annoying! Because I didn't want to lose my non-trivial edits, I had to temporarily change the "Hidden date" to something in 2021 - for a cache that I placed in 2009! I have to remember to change it back, once the bug is fixed. So please don't introduce a new bug which then leads to a message like "You cannot back-date the 'Hidden' date"! 1 1 2 1 Quote Link to comment
+Team Canary Posted March 13, 2022 Share Posted March 13, 2022 But you can place a new cache on 1/1/00!?! https://www.geocaching.com/geocache/GC9NNQ2_much-ado-a-cache-about-nothing?guid=abb22234-646f-4cc3-8af5-436544de2130 Quote Link to comment
+Radler Posted March 14, 2022 Share Posted March 14, 2022 9 hours ago, Frau Potter said: Thank you for reporting this issue. We agree that there is a bug and users will be unable to edit older cache pages until we get this fixed. We will notify the engineers and hope for a fix early on Monday. We apologize for the inconvenience. Thanks for the fast reaction! Yes, I placed the most important information into a maintenance note to keep the cache workable. Thank you! Looking forward to the fix .... Frank Quote Link to comment
+Muddy Woodies Posted March 14, 2022 Share Posted March 14, 2022 Just had the same issue here - have replaced a temporary container with one similar to the original and needed to revert the hint. Will add a note to the maintenance log and edit the cache listing when the bug's been fixed. Many thanks for actioning. Quote Link to comment
Rock Chalk Posted March 14, 2022 Share Posted March 14, 2022 Merged two threads regarding the same topic. Quote Link to comment
+solid-rock-seekers Posted March 14, 2022 Share Posted March 14, 2022 Glad to hear that this problem has been reported and that Groundspeak is working on a solution -- we bumped into the same problem today, too! 1 Quote Link to comment
+NilsGN Posted March 14, 2022 Share Posted March 14, 2022 Can confirm that the problem persist.Thank you for your efforts Quote Link to comment
+galadhdil Posted March 14, 2022 Share Posted March 14, 2022 I have the same problem, thank you for fixing it soon! Quote Link to comment
+Bl4ckH4wkGER Posted March 14, 2022 Share Posted March 14, 2022 This is now fixed. If you did indeed update your cache and are now unable to backdate it to the original date, please contact our support team via the Help Center. Please make sure to include the GC-code and date in your request. 1 1 2 Quote Link to comment
+daywalk Posted March 15, 2022 Share Posted March 15, 2022 This bug isn't fixed! I edited one of my 2017 caches yesterday night and had to change the placed date to 2021. Did some more editing tonight, tried to change the date back to 2017, still got the message that the placed date has to be within the last year. Quote Link to comment
+ChriBli Posted March 15, 2022 Share Posted March 15, 2022 1 hour ago, daywalk said: This bug isn't fixed! I edited one of my 2017 caches yesterday night and had to change the placed date to 2021. Did some more editing tonight, tried to change the date back to 2017, still got the message that the placed date has to be within the last year. Read the previous post. If you changed the date to be able to save other changes, you have to contact the support team to change it back. It is still not possible to change the date back to more than a year ago by yourself, and it is not supposed to be. But now you should be able to make changes to old caches without changing the placement date. 1 2 Quote Link to comment
+Radler Posted March 15, 2022 Share Posted March 15, 2022 13 hours ago, Bl4ckH4wkGER said: This is now fixed. If you did indeed update your cache and are now unable to backdate it to the original date, please contact our support team via the Help Center. Please make sure to include the GC-code and date in your request. Thanks a lot! It worked! And ... what surprised me most ... I could go back to the page still open with all my changes, press save, and ... ... two days later it was saved without a problem now. Not being current on web technologies I had anticipated that the site would two days later not know what this was about. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.