After manually shifting the content from the Drupal database to the WordPress websites, I needed to redirect the traffic from the Drupal pages to the new url. There are several ways of redirecting web pages and each has its pros and cons. According to several web sites, the best way to redirect is to use the htaccess 301 redirect. <\/p>\n
The htaccess redirection nomenclature is very simple and it goes:<\/p>\n
Redirect 301 \/old\/old.html http:\/\/www.yourdomain.com\/new.html<\/span><\/p>\n \nredirect 301 # the instruction that the page has moved Since I have not dismantled my Drupal installation, there were some rewrite rules in the htaccess that was messing up the final redirected url. These had to be commented out, but would result in unable to access the Drupal admin panel. In order to access the Drupal admin panel, the rewrite rules will have to be re-enabled. Example of the rules to comment out.<\/p>\n \n# Rewrite current-style URLs of the form ‘index.php?q=x’. Since Drupal could use PHP in its content, I could of course use the PHP 301 redirection and it goes:<\/p>\n \n <? The above PHP redirection could only be used for Linux servers, and my web hosting is using it.<\/p>\n Another method of redirection was to use JavaScript (code courtesy of Ryan F):<\/p>\n \n<script type=’text\/javascript’> However I did find the JavaScript version slower and in addition it would not provide good standing with the search engine and there is the possibility of losing page rank. Eventually the Drupal software would be uninstalled, so the HTACCESS version would be the best way for redirection.<\/p>\n There are of course more methods of redirection depending on what kind of servers your web site is hosted on, but basically for Linux servers, the above redirection method would suffice.<\/p>\n","protected":false},"excerpt":{"rendered":" After manually shifting the content from the Drupal database to the WordPress websites, I needed to redirect the traffic from the Drupal pages to the new url. There are several ways of redirecting web pages and each has its pros and cons. According to several web sites, the best way to redirect is to use …<\/p>\n
\n\/old\/old.html # the original folder path and file name, don’t use full http:\/\/URL
\nhttp:\/\/www.yourdomain.com\/new.html # new path and file name with full URL\n<\/p><\/blockquote>\n
\nRewriteCond %{REQUEST_FILENAME} !-f
\nRewriteCond %{REQUEST_FILENAME} !-d
\nRewriteRule ^(.*)$ index.php?q=$1 [L,QSA]\n<\/p><\/blockquote>\n
\n header( “HTTP\/1.1 301 Moved Permanently” );
\n header( “Status: 301 Moved Permanently” );
\n header( “Location: http:\/\/www.new-url.com\/” );
\n exit(0); \/\/ This is Optional but suggested, to avoid any accidental output
\n ? >\n<\/p><\/blockquote>\n
\nif(window.location.href.indexOf(“http:\/\/current-url.com”) > -1)
\nwindow.location.href = “http:\/\/www.new-url.com\/”;
\n<\/script>\n<\/p><\/blockquote>\n