08 Oct 2007
23 May 2012
Link to this post
For what it's worth, it's still a bug and I've seen no news that there's a plan to address it. However, all is not totally lost, as our team came up with a workaround for the issue. It's admittedly completely hacky, but it's allowed us to handle the issue.
The workaround uses "Allow Multiple URLs" in combination with the URL Rewrite module of IIS7. Basically, you create a rewrite rule that removes the html or aspx extension from the page you want to use as an additional URL and does a redirect to the new page. So, in your case, you would write a rule that redirects everything coming in as /<document>.html to just /<document> (It would create /directions.html to /directions in your example). Then, you add the ~/directions to the multiple URL field on the page in Sitefinity. So IIS redirects the traffic to an extensionless page that Sitefinity handles, and then Sitefinity handles the multiple URL mapping to the page you actually want to display.
Like I said, it's a complete hack and adds an extra level of redirect that simply should not be necessary - this is basic functionality that should have been available from day 1 without any weak workarounds. But, given the scenario, its the only solution that we could come up with to solve the problem.
Please let me know if this makes sense or if you need any clarification.