Jump to content


+Premium Members
  • Posts

  • Joined

  • Last visited

Everything posted by -KROP-

  1. If you look on the found list from the Profile, countries without a specified region will show as "None" e.g. for Singapore, it'll show as "None, Singapore" If you go to the cache page it'll show correctly as just "Singapore"
  2. There's a strange bug in the event calendar where all events for an owner are showing as the most recent alias used For example, user goldpot has 4 future events listed GC9TEZQ GC9WDM0 GC9WEG3 GC9WEHQ For GC9WEHQ, which is the last event, the event owner alias was changed to Purplepot. The owner name for the other events remain as goldpot. However, when you look at the events calendar, all 4 events show the owner as Purplepot Steps to recreate: Create two events Change the owner alias for the second (most recent) event to something else Click on your profile to go to your account dashboard In the top right is nearby events, click go You'll see the owner for both events are showing as the alias you set for only the second event
  3. It wasn't just with the distance from home but if you used a GC code in the location search bar, it'd give the distance as NaN. This issue seems to have been fixed and now shows "Here" as it did before this release. The distances are still imperial even though my settings are metric but I believe they are aware and working on fixing that too.
  4. Another one to add the massive list of issues with this release... If your home location is the same as a cache, the distance comes up as Not a Number instead of 0
  5. I came to report the same issue. There is nothing in the release notes to suggest Groundspeak did this deliberately
  6. Go through a user's profile and look at the geocaches they have found Scroll down until it says "load more caches". When the additional caches load they are missing the found date (see pic attached)
  7. When I'm searching for a specific cache on the app I'm usually copy/pasting it so having the "GC" prefix pre-populated just adds 3 extra button presses to delete it or you end up with GCGC12345 It adds enough extra time and interrupts the user flow enough that I.felt it worth making the post rather than just deleting it each time I do a search for a specific cache!
  8. Updating coords only allows manual typing of numbers. While this is useful for the tiny number of caches where you get written coords at a stage, it's slower for the vast, vast majority of caches where you have to do any sort of calculations. Example - You reach stage 1, paste the formula from the description into your personal notes and then calculate the final coords. Now you have no way of copy/pasting the coords into where you edit them At best you can add a new waypoint, paste the coords into the waypoint name and then manually type them to update the coords. Or I usually end up having to open the cache in the browser (which can't be done offline) Please could you allow coords to be updated by just pasting them in? Thanks
  9. The text on the Placed Date filter has gone German. I have never had german as my language setting and it's not my home country either.
  10. This is great but a while ago you took away the most useful tool for a CO - the ability to put a NM on our own caches. I still cannot work out why this was necessary. Please could you add this functionality back?
  11. I came here to report this same issue. Glad it's already being looked into!
  12. I had to use the website to redo it all manually. Missing finds is a sigificant issue with the app as that is the very core functionality! I haven't had any response from anyone at Groundspeak which is disappointing
  13. I went out for a days caching and saved my logs as drafts. When I got back to the hotel, i opened the drafts, edited them and submitted them and received the "success" message for each one. However, while some caches did indeed submit correctly (GC15C6) others remain as a smiley in my app but don't show on the site 72 hours later (GCAB9F) and others went from my drafts, but don't show as a smiley either on the site or in the app (GC6WHXW) Could someone look into this for me? Thanks!
  14. Coming up to it's one year anniversary of this bug being reported, any chance you'll fix the issue where the waypoint name is reset if you try to edit the co-ordinates? Thanks!
  15. Following on from the enormous success of the limited release of virtual caches, is there any appetite for a similar limited release of new Lost & Found events to mark the 20th anniversary in May 2020?
  16. Never say never. APE caches increased by 100% and a whole new bunch of new virtuals were released. GCHQ might change their mind and hold a block party in the future and Lost & Found might be back for the 20 year celebration in 2020...
  17. From the logs, I know they weren't even looking in the right place. It's a D4 for a reason... so yes, I've had to post an OM. But this doesn't feel like the right solution when I haven't had to maintain anything.
  18. Can I ask why this cache got flagged by the algorithm? It's D4/T4.5 and only had two DNF - one by a cacher with only 65 finds. https://www.geocaching.com/geocache/GC4XERM_hays-galleria Does this really warrant a visit to check the cache?
  19. Isn't it what the "announcements" forum is for? But Groundspeak haven't posted to that since July 2017 https://forums.geocaching.com/GC/index.php?/forum/4-announcements/ Site is down yet again. Could you advise with some timescales how long this is going to go on for? Thanks
  20. The site won't let me log in at the moment. Why are there so many problems with the website recently?
  21. I normally visit the "releases" section to complain... but this time all the changes seem positive. The suggested cache sizes are much closer to what we see in reality. It feels like the developers have been out and played the game Excellent work!
  22. How do I remove a cache from the "may need help list"? I have caches that are fine, but high D/T so get DNFs. I've logged OM but still they appear on the list. For example, I have a T4.5 cache with tree climb attribute yet people still get there and log a DNF without even attempting to climb. What else can I do? I've had to delete their DNF logs and post an OM but it still says I need to maintain the cache. This CHS seems to really discourage hiding high D/T caches. It appears to be poorly thought out and even more poorly implemented.
  23. This bug has now been fixed. Thanks guys!
  • Create New...