Quote from: simonok at Jun 17, 2008, 01:26 AM
[...] then containers show with .html and look daft [...]
I agree.
If I may be allowed to opine... One could argue (and I would) that exposing your visitors to
any file extension (.html/.php/.txt/etc...) anywhere on the site would look daft.
With the amount of usability that a CMS framework like MODx can provide, it is a mystery to me why we are going out of our way to synthesize file extensions, and in this case, going out of our way to force visitors to adhere to them, when
http://mydomain.url/folder/page looks so much cleaner, and there is evidence that this has no impact on SEO friendliness, but increases the security of your site by obfuscating the underlying framework (be it php, asp, jsp, cfm, etc...) as well as protects your upgrade path if you move to a different framework in the future. I, personally, can not come up with reasons anymore to make visitors use .html, .php, .whatever extensions to access content from a database passed through an index controller and modified with an apache rewrite handler. Are we trying to convince people that we did it the hard way? I don’t know.
The one argument
for using an extension would be if you are replacing existing static html pages with a CMS and you are aiming to prevent breaking existing links, bookmarks, and search engine indexes. If you are starting a new site from scratch, arguments in favor of using file extensions on what equates to function calls to the index.php controller are thin at best.
Again, I could be totally wrong. Just my opinion (1 of almost 12,000 users here), and of course I reserve the right to be totally wrong
In any case, the SEO Strict plugin is certainly the best way to accomplish what you described in the original post.
-sD-
Dr. Scotty Delicious, DFPA.
