wsgaskins

I see it formatted incorrectly... thats probably what you meant to say as you probably wouldn't praise something for working properly that way Actually, what HH said is that is exactly the same behavior that I see when I view GCT179 in Internet Explorer (6.0). But in Firefox (1.5), the text goes back and forth between correctly formatted+encryped and smushed together+decrypted. Thus, in Firefox, I never see the correctly formatted+decrypted. Additionally, in IE it seems that the third time clicking on the button causes the page to reload so that the encrypted+correctly formatted version shows up again. Very strange!

I'm seconding the issue with the multi-line Hint decrypt problems. The javascript decrypt function that is included now seems to completely ignore line breaks that are included in the original hint. I tried to enforce a line break with the <br> tag, but the hint edit box on the 'edit listing' page seems to strip out any html tags after I hit submit ("Edit Listing" button). I checked this on my end using FireFox 1.5 and IE6 (on Win2k) and the bug seems to appear in both cases. Quick example is from my cache - GCRHP2, but others have shown better examples (GCT179) where the cache hint is *many many* lines. Please don't tell me that this new 'feature' is just to try to enforce people keeping their hints short. I'd prefer to have a well thought out hint, but just go trying to enforce that! Can this be fixed? Please? Pretty please?

Jaz666 - As I suspect was examined by others earlier in this thread, I downloaded the GPX from your cache page, and in importing it into GSAK, I only get the 6 question waypoints -- JAQCFM - JFQCFM. Looking inside the GPX file also did not reveal your prized final coordinate JGQFCM. <wpt lat="53.8542166666667" lon="-1.86006666666667"> <time>2006-01-20T11:10:14.2970000-08:00</time> <name>JFQCFM</name> <cmt>Question 6</cmt> <desc>Which direction is this facing (roughly)?</desc> <url>http://www.geocaching.com/seek/wpt.aspx?WID=9231fe9b-2261-41dc-9e46-38dbd0ceb609</url> <urlname>Question 6</urlname> <sym>Question to Answer</sym> <type>Waypoint|Question to Answer</type> </wpt> </gpx> I didn't try setting up a PQ to grab this cache, so I can't comment for that one, but it seems like you, as the owner, are getting a different GPX file download than the rest of the world will get. So, your secret's safe with Jeremy (& your reviewer). --------- Side note/request: Can the search page be updated to allow me to find the cache page associated with a waypoint created with this new feature? For example, when I enter "JEQCFM" in the waypoint search box, today it tells me that all waypoints must begin with 'GC'. I feel that it should go ahead and do the search for GCQCFM for me.

I don't know if it's just me, but I actually prefer alphabetical order. When I have a series of waypoints all related to the same GCxxxx entry, I like to add a *suffix* to the thing so that they all show up beside each other in the list, both in GSAK and CacheMate. Is there any consideration of making the 'prefix' into an optional suffix for Pocket Queries? I know that this wouldn't work for those with a GPSr that only handled 6 chars, but so many new ones handle more than that now. Elsewise, I may have to break down and learn GSAK scripting and write myself a nifty macro to do this. Thanks! wsgaskins