LivingInNarnia
-
Posts
96 -
Joined
-
Last visited
Posts posted by LivingInNarnia
-
-
2 hours ago, SerenityNow said:
7 days ago we emailed the local reviewer who published the first cache in question that needs attention and have received no response. He lists on his profile page that email is the proper way to contact him. He states that reviewer notes will not be seen unless the cache is on his watch list. He states that messaging is not available for reviewers so email is the proper method of contact. Yesterday, we emailed the person that reviewed our second cache that needs attention. No answer yet. I posed a question in my last post to this thread and have gotten no response.We are wondering if we are being ignored because we asked a question that no one can answer until proper response can be retrieved from administration. It seems simple enough and we are sure the problems on these two cache pages can be quickly resolved by the right person. We hope we don't sound as if we're ungrateful for the work the reviewers or Groundspeak do. We're just trying to be a responsible cache owner and trying to resolve a problem that arose from Groundspeak's actions, and not our own. How should we proceed with getting answers?
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.
-
59 minutes ago, SerenityNow said:
We have two puzzle caches that were published in 2008 and 2009. On both caches, the fake coordinates were outside of the 2 mile limit of the final. Reviewers allowed the distance to be further back then. In both cases, we need to move the final spot very slightly, about 20 feet in one case and about 100 feet in the other case. We like keeping older caches so that cachers can fill their Jasmer Challenges. However, with the new editing feature, we cannot make a single change to our cache page because we get a notice that the final is more than 2 miles from the fake coords. We sent an email to our local reviewer about 5 days ago about the issue on the first cache we needed to change and have not heard back. Do we need the reviewer to make the change or does Groundspeak need to make the change. It is our fake coordinates that we need to change to bring them within the 2 mile limit.
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!
-
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.
-
14 hours ago, 4cycle said:
I was trying to check out the "New" cache editor and every time I click on the Edit button on one of my caches, I get an "ERROR 500" message. This happens both on my PC and iPhone. Anyone know what may be causing this?
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!
-
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
-
15 minutes ago, Viajero Perdido said:
It's a depressing shift in attitude, from flexible to rigid. From judgement calls by cachers & reviewers to rules enforced by code.
Any stated reason why?
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.
-
.png)
2
-
-
1 hour ago, IceColdUK said:
I could change the posted coordinates to within 2 miles of the final, and add an additional waypoint for reference but this would draw more attention to the location and the hint to the puzzle becomes less subtle. Some may say this is a good thing(!), but I'm not happy that I'm forced to rework my puzzle when nothing has actually changed.
LivingInNarnia, is it going to be possible to bypass this validation if neither posted nor final coordinates have changed?
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
-
15 hours ago, captainmath said:
The button to "Add waypoint" turns green when I mouse over it (cursor not shown in my screenshot) but clicking on it does nothing, whether I use Safari or Chrome. I don't see an option to opt-out of the new features until they work. Is there another way to add or enter waypoints?
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.
-
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!
-
26 minutes ago, Phronimos said:
Please note my newly published event is a North Island, New Zealand event, but the only way I could save changes to the cache listing under the fancy new cache edit page was to change the location to somewhere in USA. So I’ve made my changes as an American cache, and now can’t change it back to NZ NI. Fortunately the cache title says the event is being held in Hawke’s Bay, although apparently that’s in AL USA. I posted an Announcement to remove doubt.
Sorry I have nothing positive to say about your new cache edit process
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.
-
1
-
-
2 hours ago, thebruce0 said:
But how strict will the input be? Points 2 and 3 are minor variations where the coordinate format is easily gleaned from the input string.
eg, it should matter if I enter "n43 00.000, w80 00.000" or "N 43 00.000 w80 00.000", or for other locales use comma instead of period... with those concessions (whitespace, localizations, etc) be built in to the interpreter, as long as it understand the essential elements (hemispheres and degree numerics)? With free text entry I'd expect that, otherwise may as well stick with individual input fields to reduce confusion
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!
-
3
-
-
14 minutes ago, Mc Jandals said:
The Submit for Review process is simplified.... Yeah right!! Ive got a cache page already to go, every time I hit submit for review, it just doesnt happen, Ive tried this over ten times, why fix something thats not broken!!! Argh
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!
-
3 hours ago, tomastomas said:
I noticed that the coordinate verification thing for waypoints is a bit too unforgiving.
- N 59° 18.725' E 14° 36.573' is OK
- N59° 18.725' E 14° 36.573' is NOT OK
- N 59° 18,725' E 14° 36.573' is NOT OK
The detected problem in 2 above is a missing space between "N" and "59"
The detected problem in 3 is a decimal comma instead of decimal dot.In none of these cases the website tells the user what the problem is. Either you get a "Please enter valid coordinates." or "Please enter latitude and longitude values in DDM format only.". What does DDM even mean? An example of correctly formatted coordinates would be more helpful.
Why not use the same verification rules as the "corrected coordinates" field uses? It seems more forgiving and at least can parse the number 2 version above.
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
-
8 hours ago, yellow.warbler said:
If I happen to accidentally delete the link to a Related Webpage on an old puzzle, and forget to input the new link (which I am apt to do because I am very spacey), then that field would be removed from my old puzzle forever and I'd have no way to fix my mistake and put the Related Webpage back. They should at least give a warning when you are about to do that on an old cache but I highly doubt they will.
Thanks for the feedback, we'll take this into consideration as we make updates/fixes to the page.
-
4 hours ago, The A-Team said:
I'm seeing the same thing on any disabled or archived caches. This box seems to have replaced the red text that used to indicate that status a bit lower down on the listing page. This change, along with the inability to upload images to an archived cache - without any release notes - makes it feel like these are changes that weren't meant to be rolled out yet.
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.
-
23 hours ago, merlot58 said:
Like me Phronimos lives in New Zealand and we do not have States or Provinces in our country but before the new changes we were able to choose North Island or South Island. Now we are unable to edit our submitted cache pages as the State/Province drop down box does not recognize North or South Island despite the option being there. I have proved this by changing my country to US and choosing Alabama and I successfully edited my cache. When I choose New Zealand and North Island, I get a red error saying please choose a State or Province (see attached photo) and any edit I have done is not saved. Can this bug/error please be addressed
We are aware of this bug and we are looking into it! Thank you for reporting here. UPDATE: this bug is fixed.
-
15 minutes ago, The A-Team said:
Argh. IE11 bites again. I'm not seeing tooltips for any attributes in IE11, but they work fine in Chrome.
Darn, we'll look into getting that fixed (and for Firefox too!) Thank you!
-
7 minutes ago, The A-Team said:
If just icons are going to be used without the accompanying labels, then there at least needs to be a tooltip on each one so they're more identifiable. Right now you get nothing if you hover over them. Yes, you can click on the link to visit another page to look up what each attribute is, but that information needs to be available on the icons with either a label or tooltip.
Tooltips should be there! Is there a specific attribute for which you are not seeing the tooltip?
-
1
-
-
1 hour ago, niraD said:
Nice! It always felt clunky going to other pages to do these things.
Note that the reverse is not true. I can select a higher terrain rating, then select the wheelchair attribute, and the higher terrain rating remains.
And there's an interesting edge case: When you first edit a T1 cache, you can raise the terrain rating, and it will let the wheelchair attribute remain. But if you then select T1, it will tell you that it is enabling the wheelchair attribute, and from that point on, raising the terrain rating will remove the wheelchair attribute.
Have you tested this with colorblind users to see if the shades of blue and green that you use can be distinguished by them?
The size ratings are still vague, and confusingly different from the more precise ones listed on the Cache container sizes page:
-
Micro: about the size of a film canister or sm... (truncated from: about the size of a film canister or smaller)
vs "less than 100 milliliters" -
Small: about the size of an apple
vs "100 milliliters to 1 liter" -
Regular: about the size of a shoebox
vs "1 to 20 liters" -
Large: larger than a shoebox
vs "more than 20 liters"
Do the differences reflect a deliberate change in the definition of the size ratings? If so, are existing caches "grandfathered", or are owners expected to update their size ratings according to the new definition?
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.
-
1
-
Micro: about the size of a film canister or sm... (truncated from: about the size of a film canister or smaller)
-
Thanks niraD. I guess I assumed when a submitted cache is disabled (by a reviewer), it should in theory get a CO's attention. Not to mention the CO gets an email too. So to me the idea is just plain weird.
GeoMuBa notes s/he can't change the cache type. I hope that gets fixed because I do that all the time.
Something I forgot to mention. The reason I noticed these changes was because I've been struggling with the idea of using the onsite checker. I have over fifty puzzles that don't require a checker but finally broke down and decided I'd add one anyway. Insecure people like confirmation. But unfortunately, I can't. It won't save.
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.
-
58 minutes ago, thomfre said:
Lots of great changes
But can you please consider adding back the related web page field? I've seen that used (and used myself) for mystery caches many times...
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).
-
1
-
-
Thanks for letting us know - I've notified our engineering team and we'll work on getting this bug fixed. Thank you!
-
Loading issues should be resolved now for all browsers - please let us know if you continue to have issues, thanks!
-
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:
.png)
Missing lookup code for waypoints
in Website
Posted
@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!