Documents becoming containers

If I create a document called ’testing’ then it can be accessed with ’testing.html’, however, if later on the document is made into a container then ’testing.html’ no longer works, and it has to be accessed with ’testing’ since it has become a container.

Is this an intention? Wouldn’t it make a little more sense to keep the testing.html as a working link?

Thanks.

I would say that it’s very much their intention. When you’re using alias paths for SEO, you don’t want .html in the path. Imagine this if "Products" is your folder:

bogus:
mysite.com/products.html/myfirstproduct.html

normal:
mysite.com/products/myfirstproduct.html

So I’m pretty sure you’d be outvoted on this. But I would question the need for using ".html" at all. Take a deep breath and ditch the ".html" altogether.

final:
mysite.com/products/myfirstproduct

But if you’re doing it in Revo BE CAREFUL. Don’t delete the whole HTML Content Type, only the extension (I made that mistake and crushed my whole site and had to go into the blessed database to fix it - others have too, I saw a guy do it last week). They will supposedly be guarding for this in future versions of Revo. Instead, you click on the extension and edit there - no helpful prompting, unfortunately, you just have to know.

Cheers

Good points, I agree with you 90%...lol. Anyway the next site I do I will ditch the .html extension completely and see how that works out.

For now though I am going to use Redirector to redirect any necessary html files.

Is your site live already?

If not you would be better off ditching the html extension before launch (easy to do) rather than having the end user remember to redirect every page that becomes a container.

It’s best to avoid redirects if you can as it causes a delay in loading pages and may place additional load on your server.

Its not live yet. I’ll remove the html extension.