bootron

The site is functional again.

Should be fixed now This should be fixed now.

Confirmed that this is a bug, I will make sure this gets fixed today.

This issue should be fixed now. Thanks, bootron

This is definitely a bug, we are working to get it fixed. Hopefully by end of the day. Thanks, bootron

The most widely-used third party providers were given several weeks of notice. We made the decision internally to do standard release notes for this release since people can make the changes to their own profile at any time going forward.

We do not have any plans to open up the ability to use a subset of javascript at this time.

We are looking into a fix for the links so they will behave more like standard html links.

We have been making various changes to the website and mobile app in order to support GDPR issues and also PCI Compliance and general security concerns. This particular change is more about the latter two than it is about GDPR. bootron

We are working on a fix for this. Sorry for the inconvenience. bootron

I am trying to recreate this issue and not immediately seeing what the problem is. Can someone provide the specific set of steps to reproduce the error? Here's what I tried without any problems: 1. navigate to http://www.Waymarking.com/waymarks.aspx 2. Make sure waymark tab is selected 3. type coords directly in the textbox that reads "(optional address or postal code)" 4. Press "search" button OR 1. navigate to http://www.Waymarking.com/waymarks.aspx 2. Make sure waymark tab is selected 3. click on the "additional search options" link 4. click the "coordinate search" tab 5. enter coordintaes 6. press "use these coordinates" button 7. Press "search" button Both of these methods work for me on the waymarks page and also the home page. If you are experiencing something different with either of these methods or trying to do a coordinate search differently, please lay out your steps here to help me figure out the issue. Might help to include the actual coordinates you are using as well. Thanks, bootron

Had to restart the server, should be good to go now.

FYI, this has been fixed now.

This should be fixed now.

FWIW, search is back up and running for the time being. We'll likely see some ups and downs in the next few days while we work on this.

Wayfrog is correct, we are making some efforts to get the search index into a more healthy state. We've been re-indexing the data and upgrading the software under the covers, but in doing so we've had a few hiccups including the one we are experiencing right now. Hopefully within the next few days we'll have it in a better, more reliable place. Sorry for the inconvenience. Bootron

At the end of June we experienced some downtime on our API which likely affected some users. Since that outage, our services have been fully functional. We have been testing this process with our own Garmin 7x0 devices and are no longer experiencing any issues on our end. Also, for all of July all calls from all devices to our APIs are behaving as expected. That does not necessarily mean the problem is solved, but we do feel pretty confident that our APIs during this month are not the culprit. It sounds like many of the issues you all are experiencing have to do with the bluetooth connection to your mobile device. If this is where you are having troubles, this is not a place where our API is a part of the flow and could be a Garmin side issue (but we can not say this with any certainty). We are in communication with Garmin about this issue and are working to figure out what the problem is. If anyone continues to have issues after re-registering your device, it would be extremely helpful to us for you to post some more detail about exactly what your experience is like so we can work with Garmin to get to the bottom of what is happening.

The Waymarking website should now point to these forums correctly now. bootron

Ah, good catch. This is definitely a bug that we will fix. Thanks for the heads up.

So we are a little quicker to fix this than I expected. Jason, the engineer who has been spearheading this project, has already completed the fix that will add the original cache type icon back if the DNF is toggled off. We've deployed it already and it should be available for you right now. As for the isolation of DNFs, we do not have plans to make an immediate add for this feature. There are several options for how to accomplish this, and we might prefer to go through the main search to achieve this, rather than a filter that doesn't match anything we already are providing on the map page. So that's where we stand for now. If you have any other thoughts, or notice any odd behaviors, please continue to keep us posted. Thanks, bootron

Thanks for all the comments so far on this feature! We are reading through them right now and determining the next course of action to take. I definitely see the point about putting the original cache type back when the DNF is toggled off and am talking with our engineers right now about the technical feasibility of making this change. I also see the point about how cool showing only DNFs on the map would be, but that one is a little trickier from a UX standpoint. Once we decide, we'll either deploy the updated functionality or get back to you with a reason why we are holding off. Thanks again for playing with all these new features and providing us with such great feedback, it is definitely helpful! bootron

Thanks! By the way, stats should be updating correctly now.

FYI - we had to swap out our Waymarking cache servers for statistics a couple weeks ago and as you can tell a few bugs were introduced as a result. We are looking into this and will likely have a fix by tomorrow. We've already restored the charts for the per month visits and posts, but there's a few more additional things to do to get it back up and running correctly. Thanks, bootron

Okay, this issue should be fixed now.

Yep, I see this too. Will try to get a fix out asap.