Going-to-camp provider campground listing not working about camply HOT 5 CLOSED

@acaloiaro FYI. https://washington.goingtocamp.com/api/resourcelocation/rootmaps is giving a 404 response

from camply.

I'm getting errors trying to create a booking in the browser as well. It appears as though they're having an outage.

E.g. this URL is generated by their web application, and I see a 404 in the javascript console of my browser during page load: https://washington.goingtocamp.com/create-booking/results?resourceLocationId=-2147483593&mapId=-2147483561&searchTabGroupId=0&bookingCategoryId=0&startDate=2023-05-01&endDate=2023-05-08&nights=7&isReserving=true&equipmentId=-32768&subEquipmentId=-32764&partySize=1&filterData=%7B%22-32759%22:%22%5B%5B1%5D,0,0,0%5D%22,%22-32708%22:%22%5B%5B1%5D,0,0,0%5D%22%7D&searchTime=2023-04-04T12:06:18.134

After selecting a site and clicking "Reserve" also results in an infinite spinner with a "Securing your site" message.

from camply.

GTC actually did remove the rootmaps endpoint. I refactored to use a different endpoint that seems to be doing the trick, but I'll need to do a bit more testing before I'm confident.

from camply.

@cpwang96 There's a fix for this that should be ready soon, once I get some input from @juftin on the pull request.

from camply.

🎉 This issue has been resolved in version 0.16.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

from camply.