Thread

Hey there -

I’ve just completed a EE2 addon that is a simple redirect manager for EE2.  You can use it to either redirect non existent URLs to another location or you can use it in a migration situation where you need to run 301s or 302s to update URLs but don’t want to mess with htaccess.

All of the redirects are saved in a database table and appear within the Extension Settings.

Any feedback and/or comments are welcome.

Enjoy

View Download Page and Instructions

[Mod Edit: Moved to the Community News forum]

Looks really good. Been wanting something like this for a while.

Please pardon my redirect noob question…

I’m restructuring my site a little and would like to change the name of the template group that has my blog templates in it from “site” to “blog”. If I go through all the templates and change urls where necessary, and I use this plugin, can I redirect the old urls to the new urls with the new template group name in them?

Like this…
blah.com/site/blah—> blah.com/blog/blah

Thanks!

Absolutely Mike -

For the old URI you would put site/blah and the detour the full URL http://www.yoursite.com/blog/blah and choose 301, which is a permanent redirect.  That way google will know that your old URL has changed and all users will be directed to the new page.

Hope that helps!

Mike

Hi,

I’m not sure if I’m missing some step in the setup process, but the redirects are not working. I can see the extension and can add redirects in the CP fine, and they are being stored in the database without any issues.

For example, I put in:

test123           http://www.yahoo.com      301

Then I navigate to:
http://www.mysite.com/test123

But upon doing that, I get a 404 not found.

Am I missing a required step to “publish” or “activate” the redirects?

Thanks,
  Travis

I also can’t get this to work.  I’ve installed it and can add or delete redirects, but they are not working.

Any ideas?

To anyone getting 404 pages instead of the redirect, this plugin is not compatible if you use an ErrorDocument directive from .htaccess.  When the extension does get hooked into, it’s for rendering the 404 page, not the original URL.  Your two options are:

1) Make sure all URLs get passed into ExpressionEngine’s index.php.  Considering using an exclude list instead of an include list
2) Manually patch the plugin source to use $_SERVER[‘REQUEST_URI’] instead of EE’s uri object.

Details: https://github.com/cityzen/Detour/issues/3

Can this also be used to redirect an URL with an ID in it?

E.g.
http://www.mysite.com/articles/display.php?id=1000
http://www.mysite.com/articles/view/1000

This seems like an excellent way to deal with redirects and stay out of the cumbersome htaccess file. Look forward to trying this out.

is it possible to use this if the old site was on a different server?  I’m having a hard time wrapping my head around trying to create a 301 redirect from an old site hosted on a private server to a new ee site hosted on dreamhost.  will this work at all?