skramble

Done, thanks for your insight and for the suggestion.

Thanks, but I've tried toggling the "Bug Image" dropdown to no avail. ...Is there a lackey in the house?

Thanks, but I've tried toggling the "Bug Image" dropdown to no avail.

Are you thinking that something (perhaps the GUID or other ID to the default picture) isn't getting set right? All of my TBs that I checked on look good, but I haven't set up or changed the default picture on any of them. Actually, it doesn't work for yours either... for e.g., going to http://img.geocaching.com/stats/tb.aspx?guid=9e9eaa6e-cfda-4652-b146-ab36b418a266 shows me: (the generic bug again, instead of that nice patchy eye image you have set for its default image) It's the image in the "stats" link, not the TB's page, that's broken.

That =isn't= working fine for me (I was using a valid GUID, just showing the format with the x's). I see a generic TB icon above the stats of the one you posted, do you actually see the TB's real image? Just tried 3 browsers, 3 OSs, two computers and an Android... same thing. Any new luck? I'm not having any problems on 3 computers and an iPhone No, it still isn't working, and the shot that Palmetto pasted in showed the generic image, which is my whole issue. It does not show the correct image for that TB. To clarify further: At http://support.Groundspeak.com/index.php?pg=kb.printer.friendly&id=10, section 2.2 list item 3. displays what you should see at http://img.geocaching.com/stats/tb.aspx?guid=96d16114-bebf-4d5d-a75f-6fbea5c0fab4 as being: what I actually see when I hit that link is See my point? Which one do you see? If you see the correct image, something =very= strange is going on at my ISP.

That =isn't= working fine for me (I was using a valid GUID, just showing the format with the x's). I see a generic TB icon above the stats of the one you posted, do you actually see the TB's real image? Just tried 3 browsers, 3 OSs, two computers and an Android... same thing.

Anybody have any insight as to why http://img.geocaching.com/stats/tb.aspx?guid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx no longer functions as expected?

Until very recently, incorporating <img src="http://img.geocaching.com/stats/tb.aspx?guid=xxxxxxxxx"> in a profile displayed a TB's mileage below its image. Sometime over the past few days, that image has been replaced by a generic TB icon. Did something change permanently or is this a transient issue?

Works for me.... did you specify enough of a search radius to get the cache(s) you were expecting? I can not enter anything into search radius, which may be the problem. (Windows 7, IE 11)I'll wait... If you don't enter an origin location in the main search box, you won't be able to set a distance. That wasn't real obvious to me. I went straight to the "filters" page. Once I updated the filters and went back and entered in the location I saw that I could enter a distance value. However, it would only let me enter a value less than 30 miles. It looks like there is a lot of goodness there. The first thing I tried was a search for caches with corrected coordinates. I was hoping that I would get a list of *all* caches for which I had used the corrected coordinates, but it would only return a list of caches within 30 miles of the location I entered. I've solved well over a 100 puzzles for caches that I have not yet found and they're in locations all over the world. It hasn't been mentioned, but if the same search interface and backend code is going to be used for pocket queries i it would be nice if a proximity limit was not enforced. NYPC, re the 30 mile limit you're seeing, try searching without a location. When I filtered by "corrected coordinates" I got one of them returned from the Gobi desert, clear around the globe. I'd inadvertently set E instead of W for longitude. Answered the question as to why it never showed up on the GPS when I was in the right area. On the request list, it'd be nice to be able to export the results, either to file or to a PQ.

Since you're running GSAK you must have access to a Windows (physical or virtual) machine. You can find a tool to do what you need at http://www.rchnet.ch/spoilertool/ The page is in German, but the program will install in English. Cheers.

Thanks for constantly improving our experience, but +1 for the suggestion to give us back our plain text, either included with the HTML or by configurable notification preference. I read all emails in plain text and now I have to keep toggling HTML on/off just to see relevant info (just for one e.g.: is this new cache even in my country?).

Thanks for the suggestion, but if that's the file that's doing it I'm afraid I don't understand the mechanism. I deleted it and it got rebuilt when the unit booted (where is it getting its repopulation data from?). The cache in question was still showing as "found", too. When I examine current.gpx it seems to be only a series of tracking coordinates (I have tracking enabled) and some display preferences, but no cache info. Do you have any insight as to how this file contains the erroneous cache status? Thanks.

This has been driving me to distraction. From everything I've read, geocache_visits.txt is =supposed= to contain the list of found geocaches. It ain't necessarily so. I start with a blank slate. Load in a cache that I've found through GS via GPX copy. The GPS shows it as found. I edit the GPX to delete the line "<sym>Geocache Found</sym>". GPS shows it as not found. OK so far, it's using parallel mechanisms. I select that cache in the GPS, and mark it as Found. I note that the GPS did NOT modify the GPX (not accepting the file time stamp as definitive, I do a file compare). I delete geocache_visits.txt and geocache_logs.xml, and the wheels fall off. The cache =still= shows as found. What gives? If I now overwrite the GPX on the GPS with one that's been edited to remove the "<sym>" line as above, it again reverts to not found. The file system on the GPS doesn't (appear to) support ADS, so I'm baffled. Can anybody help me out of this wilderness? AdThanksvance.

Hey, fellow wet coasters. Have you noticed that if you zoom out until you see our southern border, Mapquest thinks we're in South America?

Try restarting your browser, and if that doesn't work, your PC...? Cheers.

EDIT: But I do see two or was it three (apparent) FTF's that you didn't whoop 'n holler about! I originally =did= post FTF (as I was quite chuff about being a newbie and getting three on one outing) but in reading other posts, it seemed to be bad form, so I edited those gloats out. I see a lot of seasoned veterans do whoop and holler about it, so perhaps it was just a "sour grapes" post I was reading. It's a great pastime, and I'm looking forward to learning more about it as I get more finds under my belt. I love being outside discovering new places, I'm even enjoying my DNFs. Cheers.

Well, this happens at times... But, just what it is that makes you think it shouldn't be there? Perhaps it was dropped just before you got there and the other one taken. Not everyone uses a cellphone. I don't see that you logged a cache that had a TB in its' inventory. I think it shouldn't be there because the last place it was logged at was visited by a person who said they retrieved a TB, and the same person said they dropped a TB in this cache, which was the last log entry before I visited. It was also still in that user's inventory. Just putting three and three together. I've been holding off logging it until I know the proper protocol, don't wanna be branded as an =irresponsible= newbie... :-) Thanks for your reply.

Did you pick up the trackable that was physically in there? If so, I'd say you should do the following: For the trackable you picked up, log it as "Grabbed from somewhere else". Then post a note on that cache and "visit" the trackable in that cache (or do the same on your "Found it" log if you haven't logged it yet). That way its visit to that cache is correctly recorded. For the trackable that was listed but not actually there, you could post a note on its trackable page saying that you didn't see it in the cache. If the cache owner or trackable owner are paying attention and care, they can mark it as missing. Makes eminent sense, thanks for the quick comeback.

Found a TB other than the one that was supposed to be in the cache (the right one wasn't there). How do you handle this situation? Thanks.