Subtext v1.9.4 "Windward" officially dropped this past Sunday, and pretty quickly several users and developers pointed out that the new Sitemap implementation was some-what busted. It's never good when a new feature is broken straight out of the box.
I take full blame for the foul-up. I wasn't aware of Google's apparent requirement that the Sitemap file live as close to the root of the site as possible. So when I tried to make the HttpHandler be more specific I accidentally broke the implementations in Google's eyes.
The Fix
To fix my screw-up, I had to change the Regular Expression that Subtext's Sitemap HttpHandler uses to match a web request's URL so that it is less specific. Technically, we want to match any request where the URL ends with Sitemap.ashx.
If you're already deployed or upgraded to Subtext "Windward" you just need to make one small tweak to your web.config file. So open your web.config file, and find the <HandlerConfiguration> section, make sure that the entry for the Sitemap looks like this:
<HttpHandler pattern="(?:/Sitemap\.ashx)$"
type="Subtext.Web.SiteMap.SiteMapHttpHandler, Subtext.Web"
handlerType="Direct"/>
Updated Release Files
Last night I updated the release files on the SourceForge download servers so they already have the fix baked in. So in the case that you've not already upgraded and/or deployed Windward, just grab the latest copy off the download servers and you should be good to go.
Again, sorry for the foul-up... it's my bad! But hopefully the instructions in this post, and the updated release files will help to get me back in your good graces.
Technorati tags:
subtext,
sitemap,
google