geoawareUSA9

Plenty of folks use magnetic hide-a-key containers, but these are not waterproof by any stretch, so they go through a lot of plastic bags. I get pretty good results with using PET preforms (which are pretty waterproof and durable) and just gluing magnets to them.

I don't see the error when I click the link, but I do get a 404 error when I try to view OP's profile. So perhaps therein lies the issue.

Based on @MartyBartfast 's response, this appears to be a firmware bug with tour tablet and not a geocaching website or app issue. But it may still help the Groundspeak engineers if you provide your firmware and software versions, and specify whether you're using the website through your browser, or the official geocaching app.

Moved to trackable forum. The travel bug clings one sees are generally purchased and not made, and include a TB code to be activated.

It also appears some of the stats don't get updated now until you post a new log, then it all catches up. That also makes sense, and may be the more accurate answer.

Could just be a latency. Check back in a day and see if your stats catch up.

Merged in a related thread about missing GIF image

I once found this night cache with a "reactive light" stage - when light shone on it, it lit up to reveal itself. It likely worked with some sort of light-detecting cell. I would think this better than having a flashing light going off all the time, both for battery life and for concealment. But I don't know excatly how it worked. Perhaps its last owner @Schlauwiner could shed some light (pun intended).

This is already an option for premium members. If you go to the search page and select the "filters" box to the right of the search bar, "needs maintenance" is the first attribute on the list at the bottom of the filters. It also can be done with a pocket query search - if you scroll down to attributes when building a pocket query, again, "needs maintenance" is the first attribute displayed.

I edited out the unauthorized app. If you need help with that one, you need to go to their forums.

It seems this thread has run its course and devolved into unrelated issues.

But what would you do next if your note was ignored by the CO, or the CO flat out refused to comply? I won't speak for @Keystone, but in either situation, I'd disable the cache until they responded. If they were ignoring my notes and continued to simply ignore my notes, eventually, I'd archive the cache for their failure to ensure the cache was compliant with the guidelines. If they responded but refused to comply, then I'd direct them to Appeals.

If the owner hasn't responded, you can of course return to the cache where you left it, get the code, and fix this yourself. If that's not possible, leave a note on the cache page, noting the TB is there and needs to be grabbed, and on the TB page, noting the GC # of the cache where you left it.

Thank you enabling! Owner maintenance is not possible, due to the 500 error bug. I guess the new logging feature QA-team forgot about the former Premium Members Perhaps you should edit the cache to make it accessible to all members, so you don't run into this error again. If you need my assistance in doing so, let me know.

p.s. Don't forget to post an owner maintenance log.

Could be related to this thread. It may help to share your iOS and Safari versions. Is it happening with any other browser?

I have enabled it. If you would like to make it available to basic members but have difficulty doing so, let me know.

There is a "recalculate distance" option available to TB owners to do just this. On the TB page, under the tracking number, look for a section headed "Actions" (auf Deutsch, „Aktionen"). One of the options should be "Recalculate distance" (auf Deutsch, „züruckgelegte Strecken neu berechnen"). Viel Spaß and greetings from Texas.

There is no option for geocaching.com to send you a text message. Notifications are done via email - click the link for more info. Some cell phone providers will give you an email address that will come through on your phone as an SMS, though the formatting usually leaves something to be desired. I did a quick forum search and couldn't easily find the thread, but I know it's been discussed here in the past.

Is grabbing the travel bug not an option when she inputs the 6 character code for the TB?

2) Maybe he enters the coords in a different format? That's my guess. @mrlgrose, you need to ensure that whatever app or device you are using to record coordinates is using DD MM.MMM format - degrees, minutes, and decimals of minutes, which is the format used for geocaching. If you can't figure out how to change the setting on the app or device, basic math normally works: - if your app or device is measuring in decimal degrees (DD.DDDDDDD), simply multiply the decimal places by 60 to get decimal minutes. - if your app or device is measuring in degrees, minutes, and seconds (DD MM SS.SS), simply divide the seconds by 60 to get decimal minutes.

The user name and password should be the same for adventure labs and geocaching, so she should be able to just log in using Oceanfree and the associated password. Someone will correct me if I'm wrong, but I believe the adventure lab app records which lab stages have been visited with it, so once she logs in with her old user name and password, the lab stages she has already visited should be unlocked. She'd still need to put in the answers for each stage to get the finds, though.

There can be a delay. Or sometimes the cached data (no pun intended) on the app needs to be refreshed by restarting the app. As a reviewer, I can see the language you added to the description for your hide, and it shows up both in the website version and the Android app version of the cache description. So, you're all set.

Well, first of all, guidelines can change, and reviewers can make mistakes. Which is why the guidelines state that prior cache hides should not be viewed as precedent. But, like @egroeg, I see at least one difference that directly relates to the issue your reviewer identified. GC4NNPW can be done with a GPSr or by figuring out where the photo was taken, as evident on the cache page: (emphasis added) Your unpublished cache (which, for the record, only you and reviewers can see) lacks that option. The only thing you provided that is related to coordinates is to let people know that the cache is 1 mile from the posted coordinates. That's not sufficient use of GPS technology, so your reviewer rightfully pushed back. For future submissions of this type, if you add an option where GPS can be used, or otherwise incorporate GPS usage into your puzzle as your reviewer suggested, you'll be fine.

I removed the tracking code from your post, as regular forum users are not going to be able to help you. Groundspeak controls travel bug codes. I would recommend you contact the Help Center with this issue. Give them the TB code and activation code, and they should be able to help.