Friendly URLs

Hi, I have FURLs turned on and they are working ok and I get /page.html. My problem is that when I input /page (without the .html) I get a 404. How do I get both /page and /page.html to work. I don’t know what setting to change.

Thanks,
Crawford.

That depends on why you are trying to do that, and also which version of MODx you are using.

My client has a bunch of addresses already out there that don’t have the .html so he would like them to still work.

The version is MODx Revolution 2.0.0-pl rev7212.

Can anyone offer advice on this? I need /page and /page.html to work. I only get /page.html working.

Quote from: scottishbullet at Oct 20, 2010, 02:05 PM

Can anyone offer advice on this? I need /page and /page.html to work. I only get /page.html working.

Remove the .html from Content Type for HTML and maybe create a rewrite/redirect rule to 301 .html to without .html?

Or, you could put page.html inside a container called page and use FirstChildRedirect.

I guess I am missing something here. For all my Evo sites it was already built in that with or without the extension it would resolve to the page. I don’t understand why this wasn’t retained in Revo. It’s a step backward not forward.

This is also the case for other plugins that are being used on hundreds of sites. I just don’t understand why Revolution was released when components that have become a standard are not available? Revo was supposed to be an improvement and in many ways it is but in some key fundamental areas it’s not. I have many sites I’d love to upgrade but can’t because of these issues. It’s very frustrating.

Quote from: scottishbullet at Oct 21, 2010, 11:31 AM

I guess I am missing something here. For all my Evo sites it was already built in that with or without the extension it would resolve to the page. I don’t understand why this wasn’t retained in Revo. It’s a step backward not forward.

This is also the case for other plugins that are being used on hundreds of sites. I just don’t understand why Revolution was released when components that have become a standard are not available? Revo was supposed to be an improvement and in many ways it is but in some key fundamental areas it’s not. I have many sites I’d love to upgrade but can’t because of these issues. It’s very frustrating.

I’m sorry you feel that way, but I do feel this was an overall improvement in strict URL handling in Revolution, and will be further improved as we move forward. IMO, Evolution is much too free about allowing access to files from multiple URLs without properly redirecting them using a 301 status, which is important for search rankings and avoiding duplicate content penalization. You problem is simple and can be solved with a simple rewrite rule OR plugin attached to the OnPageNotFound event which handles your case of redirecting URLs with a 301 status, to the canonical URL, of which there should be only one. So decide if they should have .html or not, and redirect the others to the one you choose.

Thanks for the reply Jason. Don’t get me wrong. I am a huge MODx fan and use it on 90% of my sites and I do think Revo has a ton of improvements. I just got caught of guard when something that used to work no longer does and there was no documentation about it. I’m not a technical developer so your comments were over my head but I’ll pass it on to someone who can hopefully help me.

Keep up the great work.
Crawford

What I did to solve this was to add a new Content Type to the system. You have to do this directly through the DB "modx_content_type". You have to go directly through the DB because the manager interface requires a ext value be present to submit the form but the overall system does not need it to function.

Create a new entry the exact same as the HTML entry , give it a name of "NoExt" (or whatever you like) and leave the file_extension "null".

Then just assign this content type to the pages instead of HTML.