Bl4ckH4wkGER

All issues raised in this thread have now been resolved: The warning copy was updated The warning no longer applies to internal pages and API partner links Players have the option to indicate that they don't wish to be warned for a particular link in the future (note that this requires a cookie which is good for 30 days). Thank you for your patience while we were working on these items.

Appears there is another layer of validation then. My apologies for the inconvenience. @eM.und.eS The bug surrounding cache size filtering is now fixed. The results will reflect this the next time the respective PQs are re-run.

Your report is missing crucial information about which search you're referring to - new search results or old seek/nearest. Works as expected for me on new search. If you're referring to seek/nearest, it would likely be a side-effect of a similar report from yesterday's PQ release. See here: We're working on a fix for that.

@DaTechniker My original suspicion about those Pocket Queries getting missed in the file system switch because they were run so shortly before it was correct. We have manually retriggered them and they should now be rerun and available for download for you. Please note that this should not count against your 10 PQ/ day allocation. Thank you for your patience. @all We're working on fixes for the other two bugs (preview issues & sizing filter) and I will let you know once those have been resolved, too.

Thank you for the clarification @Lignumaqua. At the time of my original post it wasn't fully clear to me, yet, whether the download failed on the GSAK API end for the player in question or whether it was something with the file to begin with. This has since clarified itself with the more recent exchanges. No finger pointing at GSAK intended Regarding the cache type name changes, we do have a ticket for that and Annie will let you know once it's been adjusted on the partner API.

Thank you for sharing them. I have passed them on to the engineer working this project and we will see whether we can re-trigger them. The only way would be the strategy proposed by @HHL. The download issues were present in all Chromium based browsers but not in Firefox before and due to a Google decision to block HTTP downloads - as used by the old Pocket Query storage. It is correct that with the new Pocket Query storage using HTTPS download paths that will no longer be an issue.

Thank you for bringing that to our attention. I will create a ticket so we can get that fixed.

I can understand your frustration, especially if this compromised your planning and even more so if the tools you are usually using haven't adjusted to this update, yet. That said, in the interest of actually being able to help you I'd ask you to remember that "wie man in den Wald hinein ruft, so schallt es heraus". Back to your issue: It is possible that depending on timing, those queries got caught up in the system switchover. While the new system - this includes a new storage solution - was pre-populated with all scheduled PQs of nightly runs, if you ran a manual PQ shortly before the switch, it may have happened that this was saved in the old system still. When we then switched the systems, and hence the path to the new storage system, it may have become unavailable. To fully understand what happened , we will need the PocketQuery IDs for these queries, as noted in my earlier post. In case you don't know how to retrieve them, here is how: Click on the preview icon of the PQ to open the preview Copy the ID from the URL Share it with us here Unfortunately, we won't be able to manually reset your daily PQ allocation for past days.

Thanks. I misread your original report. I was able to repro the issue with a new PQ, too, and have created a ticket for the engineers.

@Pe_Bo @6foot3 Thank you for bringing that to our attention. Could you confirm for me that the later pages contained PQs that recently ran vs old records of PQs you ran a long time ago. Very old PQs may have not gotten ported over to the new systems. I will check with the engineers on this but any additional context and detail you can provide would be helpful, thanks. @DaTechniker @Gamma5 API partners were given advance notice of these changes. GSAK is still actively working on making the needed adjustments on their end. Once they have a patch, they will let the community know and things will be back to working as you are used to As far as the mentioned unauthorized application goes, we don't test for dependencies against them and they're not given advance notice. Please reach out to them directly about any issues. That said, I don't think expecting a fix from them within less than 24 hours is fair. Please note that any further discussion of issues with this application will have to be deleted because they violate forum guidelines. In the meantime you can download the PQs via the browser on the website. If you are still missing PQs on the web also, please provide more detail about which ones are missing in particular, ideally provide the PQ ID, and when you would've expected them so we can take another look.

Thank you all for sharing your passionate and candid feedback with us. Please continue to share your feedback with us in the comments. Let me address some of the points that were made so far: I can understand that it comes as a surprise because historically Geocaching HQ hasn't completely retired many site features or pieces of game content. Hence, when we do, it appears more significant than it might be for other organizations which do so much more regularly. I can however assure you that this decisions was far from random: Benchmarking was identified as a dependency for another project that is currently in-progress and nearing completion. We aren't quite ready to share more details about it, yet, which is why it wasn't mentioned in the pre-release notes. At the time, a decision had to be made to shift course and accommodate this new dependency or to not do so and retire benchmarks. The cost to accommodate benchmarking far exceeded the cost of retiring it and so after reviewing usage data and ongoing maintenance costs, the respective decision was made. Please see further context below. Before making this decision, we carefully reviewed information regarding benchmark finds and the number of distinct players who found benchmarks in the past years. Both have been on a steady decline since 2010 and even more significantly since 2015. Most recently in the last 365 days, only ca. 2500 distinct players have logged a benchmark. This represents ca. 0.13% of players who have logged a find during that same period. Puzzles will remain solvable if the puzzle requires finding information on the actual benchmark plaque or the associated information. Those are still available by visiting the location or via research on the NGS website. Puzzles relying on finding information in benchmark logs on geocaching.com will indeed become unsolvable and should be archived. I can assure you though that this affects a very small number of caches. The fact that you never noticed how broken it actually was if anything is a testament to the hard work of HQ's engineers who frankly don't receive a lot of love here. As correctly noted by @essap2, maintaining these old pages requires significant resources. These resources can then not be spend on other improvements, including new exciting features and long standing community requests. To the point made by @niraD, Geocaching HQ is making an ongoing effort to "get the house in order". This requires updating several old code bases. While I understand that this is hard to hear, not all of them are salvageable or worth the considerable work to migrate them to a new environment. I understand the disappointment that comes with a beloved part of the game going away. While I understand that it isn't completely the same, I encourage you and everybody else to check out the Waymarking.com benchmark categories for U.S. benchmarks and Canadian benchmarks. Alternatively, you can obtain the data from the NGS directly. There are also different apps out there dedicated to benchmarking for both Android & iOS. Scraping the website constitutes a violation of the terms of use and you risk a suspension of your account if you opt to proceed this way. If you want to make this information available to others, please go the route proposed by @chaosmanor and contact the NGS directly. They'll also be able to provide you with a much more up-to-date file. The geocaching benchmarks database hasn't been updated for quite some time. I understand that it is disappointing. Unfortunately, this is an all-or-nothing situation and nothing isn't an option in this case. You and all others who feels strongly about their benchmark logs and photos have some time to save them for yourself. Starting with the List of your benchmark logs on https://www.geocaching.com/my/logs.aspx?s=3 is a good starting point. I understand the frustration and agree that there are lots of opportunities in the geocaching world and how other platforms could be integrated in it. Unfortunately, with a finite amount of resources we have to be selective in which ones we pursue. At this point benchmarking isn't one of them due to its locally restricted nature when the game as a whole becomes more and more global.

It's not only the German language package but the general localization of the map. All other options have been exhausted over time by our engineers since these reports have continued coming in for some time. At this point the only long-term solution is to completely rejig how the map is localized which among other things will need decoupling of the map and its translator and changes to how translations are rendered. These are significant changes that rebuild a larger portion of the whole map implementation. We understand the frustration and are actively looking at solutions. It's due to the size of the needed work that this will take another while.

The pages you're seeing this on, based on what I can make out from the significantly cropped screenshots, are not mobile optimized so it doesn't matter what platform you're viewing them on. The button styles and colors in your screenshot also don't match the geocaching color and styling palette at all. Here is an example of what I see on both web an mobile and Are you sure you're not running any scripts or visual packages in your browser that may override page styles? Is this only on one cache that may have funky HTML code in the description or on all caches?

While it is true that this was a bug early in the release, it was also fixed between now and then. I have notified the Engineers to investigate why this bug has returned.

Theoretically - yes. Practically where we are right now - no. Just some of the limitations: Technology limitations of the Elasticsearch data cache that is being queried Performance at scale Poor user experience of Adding-to-Lists (limited to 1000 caches) vs. results that would far exceed that - you'd need to mitigate that Poor user experience of inconsistent search experience across platforms Additional build and maintenance costs https://www.geocaching.com/my/geocaches.aspx is a very old legacy page that still relies on old poorly performing SQL queries. This kind of technology is not scalable. See above.

Please re-read my post from August 2 on how you can access this information if you have the right filters set:

In the current search experience, enter their username in the "Found by" filter and specify the "Find date" filter to be between January 1, 2021 and December 31, 2021. Then hit search. This will show you all found caches, both active and archived, for that user in that timeframe. If that should exceed 1000 results, you can adjust the timeframe to keep it under the threshold. Web searches are generally moving towards more nuanced search results instead of just dumping 1000s of results on a user. Timeboxing queries as described above is a common strategy to do so. I apologize if that doesn't meet your personal preferences but there are currently no plans to revisit how/ how many results are presented per query.

Because the Jacklinks promo was the first that was built on a more modern CMS. The latter has its own URL path within the site ecosystem. The new path will be the one you will see for trackable promotions going forward. The URL doesn't change anything about how official the page is

You can't change the coordinates of the cache because you aren't the cache owner. The state & country are based on the posted coordinates of the cache. The distance from your home location is based on the coordinates relative to your home coordinates. What you have done is entered solved coordinates via the pencil icon, which moves the icon to a different location but is not the same as "changing the coordinates." As with any other cache, entering solved coordinates only updated the pin location for you and does not update the state & country, it never has. We understand that the original Locationless Caches used to work a little different with entering coordinates in logs, etc, but as noted before that is no longer part of the these modern limited release Locationless Caches. Appreciate this one for what it is and rest assured that it won't mess up your stats, as noted by Moun10bike.

With today's release we have added another layer of security to disabling and deleting your account. In order to proceed with disabling or deleting your account, players will need to re-enter their password when confirming their intention. You may need to complete a reCapture, too. This will then enable the button to proceed. Disable your account: Delete your account: We have also added additional copy to clarify that disabling or deleting accounts does not cancel membership purchases through the app stores. Specifically, you will find the following above the “disable your account” button: Note: Disabling your account will not cancel Geocaching Premium auto-renewal payments for memberships purchased through Apple's App Store or Google Play. And the following above the “delete your account” button: Note: Deleting your account will not cancel Geocaching Premium auto-renewal payments for memberships purchased through Apple's App Store or Google Play.

This is an issue on the old Browse Map (/map) but not on the newer Search Map (/play/map). When the latter was introduced, the Browse Map was slated for retired. This decision was revisited after community feedback and the Browse Map has been kept around. That said, resources for bug fixes and feature improvements on the old map will be limited. As noted by others, due to the limited time impact of this bug, chances that it will be fixed are slim.

@Kveldulfir ist dein Internet-Provider zufällig Vodafone? Aktuelle werden anscheinend von Vodafone alle Geocaching.com-Seiten geblockt. Wende dich damit bitte an deinen Internet-Provider.

This does not appear limited to just accessing finds from the profile links, but applies across the board on search results pages. Thanks for letting us know, we've notified the engineers.

The statistics page, including the calendar grid, refreshed in intervals. It indicates on the page when it last refreshed: The leaderboard won't update after you delete a log. It is a shortcoming of the system.

Today, we released another set of small improvements to the Search Results experience: We have improved the feedback provided to players when adding caches to a List via the Add-to-List pop-up - creating parity with other places of the website You will now see more clear confirmation when the caches where added - a green checkmark You will see when adding the caches failed - a red X You will see when adding caches is not possible - a red ! The bug identified in the forums here will be part of the next sprint.