The Wonderful World of MT Redirects (5 posts)

OK, I either am an idiot or am just missing something (meaning Readme.txt wasn't clear enough). I've already imported my MT entries and that went smooth.... I downloaded Alex King's MT Redirect script, configured the .php file and uploaded it.... Rebuilt my MT entries and....
Google's still pointing to all my MT entries...
I'm lost what to do now, to be honest. The Redirect script is saved in my root folder with the rest of my WP stuff. Should it have been saved somewhere else? Was I supposed to delete my MT entries from my server (having to rebuild my entries says otherwise).
It should be a simple 1, 2, 3 thing and yet it's proving otherwise.

Those other methods all differ based on your MT permalink setup. Try my method, which is independent:
(Note, because your MT files are in html archives, you need mod_rewrite for this, so if you don't have that, stop reading)
First step is to make your server parse html files for PHP. Add this to your site's .htaccess file

Rebuild your individual entries. This makes all your entries just contain this simple PHP 301 redirect that sends the browser to wordpress asking for an entry with the exact time (to the second) as the MT entry.
Put this code in WordPress to fix the URI and complete the illusion. Put it near the top, after the wp-blog-header call, but BEFORE any content is echoed:

So here's the process: MT has generated a file with the exact time and date of the entry, with PHP code to ask WordPress for it. When the page is loaded, a 301 redirect sends it to wordpress with the date/time info. When WP sees that the time and date are specified down to the second, it realizes that there can reasonably only be one permalink for this entry. It gets the permalink that matches that time/date info, and does another 301 redirect, sending the user to the new entry.
Google will eventually catch on, and your old URIs will disappear in the search engine.

Assuming you wanted that piece of code inserted into my index.php from wordpress:
I'm getting this error now on individual entries:
Parse error: parse error, unexpected T_STRING in /home/.kafka/username/stonegauge.com/archives/entrynumber.php on line 4