Hi, I pushed out another site update tonight. Yes, they've been coming fairly often lately.
This update had some fairly extensive changes. The overall functionality of the site changed very little, however these are some changes that I've been meaning to do for quite awhile and I finally bit the bullet and implemented them.
Whenever a Geocache name or a Geocacher name is generated on the website, the name will now be properly html encoded. This is important so that your browser will properly render the name if it includes html tags. For example, presume a Geocache has the name:
Before the update, that cache's name would have been rendered as:
Boldly
Slanted
Multiple
Line
Name
The above isn't so bad, it's a well behaved example. However, a devious person could cause heartache by injecting some malicious java script into a cache name.
For pages that have paging, such as the leader boards, I have changed the pg parameter to be 1 based instead of 0 based. So now to go to page 3, pg=3 (it used to be pg=2). Zero based counting is a geeky programming thing, but the application was totally out of place. I guess I'm just a geek at heart.
Added achilles points to the GeocachePage.
This update touched a lot of code, especially code dealing with generating the links to other pages on the site and generating cache and cacher names. I tried to be thorough and performed a lot of testing to ensure I didn't break any of them, but there's a chance I made a few mistakes. As always, if you see something wrong with the site, please note where and let me know by replying to this release note.
Nice job making all those underlying changes without breaking stuff! Did some checking through the site, and I did not find any broken links. I think Groundspeak already checks and prohibits malicious or suspect code from being used in cache titles, descriptions, etc., but that's very good practice to do anyway. Thanks for building this great site!
I noticed a missed impact today. When a search results in redirecting directly to a cache page or cacher page, the numerical ID is still being used instead of the GC or PR code. This will be corrected in the next site update.
I found another missed impact. When going to a leader board (any of the points or backcountry boards) from a cacher page, that cacher should be highlighted on the board page. Using the cacher's profile code instead of the ID broke the highlighting. This will be corrected in the next site update.
