Redirects from old site using queries to new EE site

Question

I'm putting a new site live and need to redirect all the old pages to the relevant new ones. The issue is that the old site used PHP queries, whereas the new site doesn't.

This means that if I setup a redirect like so:

RewriteRule %{QUERY_STRING} range.php?type=baropt&item=01 [NC]
RewriteRule .* http://domain.com/range/bars/led-bar? [R=301,L] 

Instead of redirecting as it should, it simply displays a blank page with the message 'Disallowed Key Characters'.

I'm happy to setup manual redirects for the various pages (there's only around 80-90 in total). but can't workout how to do it. I've been told I'll need to use 'mod_rewrite, request_uri + query_string conditions' but that doesn't mean much to me.

OLD URL: domain.com/range.php?type=baropt&item=01

NEW URL: http://domain.com/range/bars/led-bar

Any ideas gratefully received!

Thanks in advance,

Tom

Answer 1

Did you actually mean this?

RewriteCond %{QUERY_STRING} range.php?type=baropt&item=01 [NC]
RewriteRule ^(.*)$ http://domain.com/range/bars/led-bar? [R=301,L] 

You should use RewriteCond, not RewriteRule is first line, as it'a conditional that applies to the rule, the rule itself is in second line. Also replace &amp ; with simple ampersand (unless you really have &amp ; in URL)

Answer 2

If you have imported the previous URL as some field, let's say, previous_url, you can use a template to help you create the redirects.

Access the template, copy the rules and paste them on your .htaccess file or NGINX location.

For NGINX

{exp:channel:entries channel="channel_name" limit="500"}
    rewrite ^/{previous_url} http://domain.com/template_group/template/{url_title} redirect;<br />
{/exp:channel:entries}

If everything work fine, replace redirect by permanent and restart nginx service.

For Apache

{exp:channel:entries channel="channel_name" limit="500"}
    RewriteRule ^/{previous_url} http://domain.com/template_group/template/{url_title} [L,R=302]<br />
{/exp:channel:entries}

If everything work fine, replace 302 by 301.

Answer 3

It's a bit pricey for what it does, but if you prefer to manage redirects from the CP, and think maybe there will be more in the future, than Detour Pro is a nice option: http://devot-ee.com/add-ons/detour-pro