bootron

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

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.

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

Okay, this issue should be fixed now.

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

So I think it's safe to say we have gotten the Waymarking site RAM issues under control. We've had 4 straight days with no morning issues so I have made a few new adjustments to the back end code to try and speed up the page load times. So far it seems to be pretty snappy. If things go back to a bad place I'll re-adjust in a day or so. Thanks, bootron

We have been seeing some slowdown issues and have been hitting some resource limits at around 7-9AM PST each day for the past several weeks. It seems to be the only time that this happens, we are trying to get to the bottom of what is causing it. We don't believe this is related to the previous problems that we had been seeing over the past several months.

The Geocaching database had a minor failure a few minutes ago. Waymarking still shares account data with the Geocaching website and so when Geocaching goes down, often Waymarking will see consequences as well. This has always been the case. It is not related to the issues we have been seeing in the past couple weeks. As far as I can tell there are no major issues happening to the Waymarking site right now and you should be able to use the site as before. Bootron

One additional thing to note is that we had to slow down the home page load time a bit by doing some of our fixes. This is a known issue at this point, and we will try to tweak the settings in the upcoming days to make it a bit more responsive. It's a trade-off at this point, between using up server and database resources, but we will try to find the right balance. Also, there appears to be a memory leak in the code somewhere (this has always been there, it's not new), and as a result we may have to reset the server from time to time until we can stamp it out for good. If we do reset the site, it should only be down for a minute or two at a time.

Been getting a lot of error messages today and the site is EXTREMELY slow. Yesterday, it was iffy. It was loading at a slow, but not too ridiculously slow. Today, it's been very slow and the site has just crashed for the 3rd time today that I know of. I wonder if this will ever be fixed. My photos from summer trips/vacations are back piling so much right now that I don't want to go anywhere and waste more space/time/energy to post waymarks that may never get published. So at about 16:30 PM PST we made some significant changes to the Waymarking codebase and also the servers themselves that we think will put the site back into a usable state for the forseeable future. I won't guarantee that it will be the end all be all solution to all our troubles, but we do think we have figured out the root causes of the past week's memory troubles. The code base still has its problems and we aren't pretending to have fixed many of the issues that you have seen over the years, but the core functionality should be generally back in order now. We'll keep a close eye on the site metrics this weekend and will be checking in to the forums to make sure that this is, in fact, the case. Bootron