Hi, I'm considering to write an intelligent "404.aspx" to address the issue of directory-like browsing in DNN. I have found this user behaviour:
When somebody is browsing through a page like this:
http://www.doman.com/Father/Page/tabid/345/Default.aspx
where "Father" is the trimed name of the parent page and "Page" is the name of the current page. The user tries to delete the "Page/tabid/345/Default.aspx" to be able to browse the parent page "Father". Obviously, the user gets a "404 Not Found" error.
I'm trying to fix this (I know it is not an error in DNN, but it affects the user experience and "directory-like browsing" is a best practice) by creating an intelligent "404.aspx" that can catch all these requests.
Additionally, I want the 404.aspx to be able to show a friendly 404 page in case the page really doesn't exists but I want to do this accordingly to the current portal and provide some way (I don't know what still) to update the 404 message for the portal using the DNN admin interface.
Anyway, this is a proposal and if you can help me with some guidance of suggestions, please do so.
Greetings