+paleolith Posted May 24, 2008 Share Posted May 24, 2008 The description for GC157PB has had its links corrupted. Unlike some of the other link complaints recently, this time it appears (emphasize appears) that the description in the database is corrupted, not just filtered for display, because my original HTML is corrupted when I bring up the "edit listing" page. I keep my description in a text file and copy and paste the description into the edit listing page, so I have a solid record of what the last edits I did were. It's not a matter of me futzing up the text in the tiny edit box. I know about that problem from experience, which is why I use a safer method. The original link is <a href="http://www.geocaching.com/seek/cache_details.aspx?wp=GC128N2&Submit6=Go">Happy Place GC128N2</a> but the edit listing page now returns "http://www.geocaching.com/seek/cache_details.aspx?wp=GC128N2&Submit6=Go"> Happy Place GC128N2 That's right, the <a> tags are totally gone, except that the closing > is left. The href= attribute is gone, though the value which follows remains. And hey, this is just a very simple link to another cache page, no added attributes or anything, though it's not the simplest version of such a link -- I forget where this version comes from. I haven't yet checked my other caches which have similar links. What's up? Edward Link to comment
+Miragee Posted May 24, 2008 Share Posted May 24, 2008 I'm not sure why the links are like that, but there are extra characters in the links that are not necessary. Try this: <a href="http://www.geocaching.com/seek/cache_details.aspx?wp=GC128N2">Happy Place -- GC128N2</a> and this: If you want routing hints, read the description of a log entry for<a href="http://www.geocaching.com/seek/log.aspx?LUID=c2797434-a8d2-4aad-8368-a601bae014c9">my preferred route</a>. One thing to keep in mind is that most "paperless" cachers won't have access to that previous log on their PDAs. You might consider having that in the description . . . just a thought . . . Link to comment
+paleolith Posted May 25, 2008 Author Share Posted May 25, 2008 I'm not sure why the links are like that, but there are extra characters in the links that are not necessary. I took out the &Submit6=Go and now it's working. But I wasn't paying enough attention, and I think it had already started working again, so I'm still not convinced it's fixed. Strange doings are afoot ... If you want routing hints, read the description of a log entry for<a href="http://www.geocaching.com/seek/log.aspx?LUID=c2797434-a8d2-4aad-8368-a601bae014c9">my preferred route</a>. Good idea, thanks, I've added the link. One thing to keep in mind is that most "paperless" cachers won't have access to that previous log on their PDAs. You might consider having that in the description . . . just a thought . . . I debated that with myself for quite a while (and my internal debates can get vociferous). I had two issues with putting it in the description. One was that some cachers might prefer finding their own route and consider it a spoiler. The other was that it would make the description a lot longer, probably a negative value for those who don't want to use it. Critically, anyone who feels comfortable even trying to approach this cache can do so safely; there are no dangers which need to be avoided by using the suggested route, just some scratches and other effects of bushwhacking in chapparal. The description does cover the bushwhacking and the need to be comfortable navigating off-trail in open terrain. As it has turned out, most finders have made their own routes rather than following mine, and seem to have been happy doing so -- I did sort of imply that finding the route (or bettering mine) could be part of the challenge. Thanks, Edward Link to comment
Recommended Posts