+Juicepig Posted October 17, 2007 Share Posted October 17, 2007 (edited) If you scroll to the area North of scarborough, Ontario, Canada - there seems to be a cache that has a funky character (or something) that is messing up the map program (IE7 only tested) The error is this: It pops up if this cache is in the screen... although I cannot determine for sure which cache it is... but i have a suspect! http://www.geocaching.com/seek/cache_detai...9e-453eb6c6dd24 Try clicking here: http://www.geocaching.com/seek/gmnearest.a...mp;lng=-79.0805 Edited October 17, 2007 by Juicepig Link to comment
OpinioNate Posted October 17, 2007 Share Posted October 17, 2007 Wonderful deductions. It is, in fact, the cache you linked to that's causing this error (the title of the cache, to be exact). We're looking at this now. Thanks! Link to comment
+TochiHunt Posted October 18, 2007 Share Posted October 18, 2007 Oh awesome! I had ran into the same problem scrolling through the Pickering area. Opened up a ticket, posted on the google map problems thread. Glad to see this one getting fixed. Link to comment
Ranger Fox Posted October 24, 2007 Share Posted October 24, 2007 I ran into this problem when programming the waymarks back into the map (Greasemonkey). The problem I ran into was with double quotes. You can add that to your list of unsafe characters. The problem is these literals do not work with JSON deserialization. For the double quotes, I replaced them with two single quotes--pretty much indistinguishable with the font used on the page. To fix the problem from this reported defect, I replaced the backslashes with forward slashes. Unfortunately for Groundspeak, you all have to find a way to display the literals and not a way around it. I do have an efficient JavaScript function that will fix everything you need, along those terms, to display the names correctly for JSON deserialization for waymarks and geocaches. Hmm... If it'll take Groundspeak a few weeks to fix, should I put out a Greasemonkey patch? Just as long as the csae(c,o,e) function is overridden correctly, that is. Link to comment
+Raine Posted October 28, 2007 Share Posted October 28, 2007 If it wasn't mentioned, this has been fixed. -Raine Link to comment
+blb9556 Posted November 16, 2007 Share Posted November 16, 2007 It's the first / because in source code it goes.... Codehere/cachename you can't have 2 // together like that. Link to comment
Recommended Posts