Forums / Developer / URL redirects from old site pages to eZ Publish pages?

URL redirects from old site pages to eZ Publish pages?

Next topic

Author	Message
Ben Overmyer	Monday 25 August 2008 12:56:24 pm I'm involved in a project to completely revamp a website from static HTML to eZ Publish. We have a lot of disparate web pages and applications whose URLs are referenced by a LOT of documentation, as well as a few web apps with hard-coded URLs. Is it possible to set up redirects from old URLs to eZP pages? For example, I want to redirect from something like: www.mysite.com/folder1/page13.htm to: www.mysite.com/content/ezstuff/page13 Any advice is appreciated.
Gaetano Giunta	Tuesday 26 August 2008 1:04:12 pm Sure enough. eZ Publish supports a full fledged url-alias mechanism. Custom aliases can be set up for every content node or for redirecting to any module/view within the system itself. Wildcard aliases are supported, as well as the possibility to have aliases do an "external" redirect (ie. an http 301, where the user sees the final url in his browser) or an internal one. All of the aliases are set up from within the admin interface. Just make sure you are using version 3.10.1 or 4.0.1 and not 4.0.0 or 3.10.0, ad there are known bugs with url aliases in those versions Principal Consultant International Business Member of the Community Project Board

Author

Message

Monday 25 August 2008 12:56:24 pm

I'm involved in a project to completely revamp a website from static HTML to eZ Publish. We have a lot of disparate web pages and applications whose URLs are referenced by a LOT of documentation, as well as a few web apps with hard-coded URLs.

Is it possible to set up redirects from old URLs to eZP pages? For example, I want to redirect from something like:

www.mysite.com/folder1/page13.htm

to:

www.mysite.com/content/ezstuff/page13

Any advice is appreciated.

Gaetano Giunta

Tuesday 26 August 2008 1:04:12 pm

Sure enough.
eZ Publish supports a full fledged url-alias mechanism. Custom aliases can be set up for every content node or for redirecting to any module/view within the system itself.
Wildcard aliases are supported, as well as the possibility to have aliases do an "external" redirect (ie. an http 301, where the user sees the final url in his browser) or an internal one.

All of the aliases are set up from within the admin interface.

Just make sure you are using version 3.10.1 or 4.0.1 and not 4.0.0 or 3.10.0, ad there are known bugs with url aliases in those versions

Principal Consultant International Business
Member of the Community Project Board