Theniyaal

https://forums.geocaching.com/GC/index.php?/topic/350968-download-error-cant-download-Wherigo-cartriges/ There's a handful of useful posts in that thread. The short version is this app has been unmaintained for an extended period of time, and apparently a new dev team is working on fixing this seemingly somewhat common issue. There's a couple of posts that offer various solutions you could try out.

Dear everyone who designs updates: If you don't need to move a button, don't @!%#ing move them! I can't conceive of any reason why the new 'Search Geocaches' button should have taken the place of the existing 'Map Type', 'Zoom In/Out' and 'Fullscreen' buttons. Have you folks never heard of muscle memory? I appreciate the efforts to improve the site and its features, but this is one of those inconsequential things that drives me absolutely bonkers.

I'm not talking about valuing the container, contents or location. When I say it seems valuable because it's fourteen years old, it's the 145 logged visits, and the stories and photos contained within. It just seems really silly to let that all fade into obscurity by archiving it when I can just stick a lock n' lock in ground zero and keep an eye on it, and preserve all of that history. Pretty low risk for what I see as a moderate reward; worst case, it gets looted again and I'm out a couple bucks, some camo tape and some dollar store swag. Bully for your area. I already explained why my local reviewers have elected to leave this one be.

To reply to some of your posts, I actively want to avoid the cache being archived; a cache from 2004 seems valuable to me, and I've little desire to see it replaced. I'd have asked the more active reviewer for our area, but I already have a message out to them I'm awaiting a response on, and I don't want to be 'that guy'. The cache has been logged over those years, but the container had fallen into further disrepair as time went on. It was eventually field dressed and vaguely functional up until it was last found a month ago. It has since been destroyed and strewn about, leaving half a container, some scattered swag and no logbook. This is the state I found it in today, and if it took three years for a damaged cache to finally stop kicking, I don't have a problem with risking it happening again. As for why it's been flagged as NM for three years and not been archived, it seems local policy is that if the cache is being logged, it's still fit to be up. It's not until it's reported as missing or the DNFs start to pile up before a reviewer will put the word out the cache will soon be archived for non-responsiveness.

There's a local cache that's been in dire need of maintenance for over three years, and today I found the scattered remains of what's left at ground zero. The cache was originally placed in 2004, and I'd really hate to see it go to waste because of an absentee owner. The current CO hasn't logged on in three years, and with a Needs Maintenance log that spans that same length of time, it's probably quite safe to assume they're not involved with Geocaching any longer. I know that cache adoption isn't possible without the CO's involvement, but what is the etiquette on someone replacing an abandoned cache and performing the upkeep on it, even if their name isn't attached to it? I'd have no problem helping this cache continue on into its' fifteenth year, but I'd hate to do so if such things are frowned upon.

*watches clock wistfully like it's the last day of school* Thanks for the speedy answer. Now we play the waiting game.

Last night, I was setting up pages for three new caches, and while the first had no problems, the other two deliver a 'error 500' message when I click Save & Preview on the size and ratings page. I've tried backing up to the point where it asks if I want to start over or edit the existing page, and waited overnight, but I'm still facing the same problem. I can't submit either of these caches, but I don't want to scrap them and try again from fresh, thus burning two perfectly good GC codes. If anyone had any advice on how to attempt to solve this issue, I would appreciate it immensely.