I'm upgrading to MT 4.2 from MT 3.33 and I'm doing so using a fresh install. I like to start fresh with each release, as 6A says, to de-cruft my installation.
However, I'm not finding any good step by step instructions like Elise's versions for [3.2] (http://www.learningmovabletype.com/archives/001367asafewaytoupgradetomt32.php) & [3.3] (http://www.learningmovabletype.com/a/00156633safeupgrading/). LMT has an [upgrading to MT4 post] (http://www.learningmovabletype.com/a/upgradingto_mt4/), but it's very, very brief.
Specifically, I'm wondering about steps 8-14 in her post on Mt 3.3, are these necessary when upgrading to MT4?
8 - Copy any custom search templates. still needed? 9 - Compare your old mt-config.cgi settings to the new settings in mt-config.cgi-original. Using a text editor, like BBEdit, copy the relevant settings over to the new config file. I assume this is still necessary, right? 10 - Change the name of mt-config.cgi-original to mt-config.cgi. Set permissions of the cgi files to 755, with the exception of the mt-config.cgi file. Set the permissions of mt-config.cgi to 644. Note that there is also a .cgi file in the plugins > Style Catcher folder - the stylecatcher.cgi. You will need to set the permissions of this file to 755 as well, if you intend to use this plugin. All still necessary, right? 11 - Point your web browser to the location of the new mt.cgi file. The program should automatically recognize that you are doing an upgrade and it should prompt you to upgrade. Still true, right? 12 - Note that if you are using TypeKey authentication, you will need to do a template refresh of your Site JavaScript template. Is this needed? It was specific to changes in MT 3.3, as I recall. 13 - Rebuild all of your blogs. If you use dynamic publishing, make absolutely sure that you rebuild the mtview.php (Dynamic Site Bootstrapper) or it will be pointing to the wrong place. Still needed, I bet. 14 - Once everything is working, remove permissions from your old CGI scripts. After you have completed your upgrade change the permissions of the current mt-upgrade.cgi to 644. Still required, or at least recommended, right?
Is there anything MT4.x specific that one should know about doing a fresh installation upgrade?
Reported on Movable Type 4.2
Argh! Sorry about the poor formatting, it seems that Markdown missed the copy-paste paragraph breaks.
Here's a (I hope) more readable version:
8 - Copy any custom search templates. *Still needed?*
9 - Compare your old mt-config.cgi settings to the new settings in mt-config.cgi-original. Using a text editor, like BBEdit, copy the relevant settings over to the new config file. *I assume this is still necessary, right?*
10 - Change the name of mt-config.cgi-original to mt-config.cgi. Set permissions of the cgi files to 755, with the exception of the mt-config.cgi file. Set the permissions of mt-config.cgi to 644. Note that there is also a .cgi file in the plugins > Style Catcher folder - the stylecatcher.cgi. You will need to set the permissions of this file to 755 as well, if you intend to use this plugin. *All still necessary, right?*
11 - Point your web browser to the location of the new mt.cgi file. The program should automatically recognize that you are doing an upgrade and it should prompt you to upgrade. *Still true, right?*
12 - Note that if you are using TypeKey authentication, you will need to do a template refresh of your Site JavaScript template. *Is this needed? It was specific to changes in MT 3.3, as I recall.*
13 - Rebuild all of your blogs. If you use dynamic publishing, make absolutely sure that you rebuild the mtview.php (Dynamic Site Bootstrapper) or it will be pointing to the wrong place. *Still needed, I bet.*
14 - Once everything is working, remove permissions from your old CGI scripts. After you have completed your upgrade change the permissions of the current mt-upgrade.cgi to 644. *Still required, or at least recommended, right?*
Does anyone have any insight into this?