« Ignoring The Olympics | Main | Speeding Up Movable Type »
August 15, 2008
Upgrading Movable Type 3.2 to 4.2
Today, I'm going to try to upgrade to release 4.2 of Movable Type from 3.2. So the availability of the website may be a bit sketchy, but if it's down, I doubt you'll be reading this - none-the-less. Patience is a virtue. Good things come to those who wait, etc. etc.
First, I'll run another backup of the website because, my backups didn't run last night for some reason. I think that Allie is signing me off when she comes over, which prevents my backups from running. I'll have to discuss this with her at some point, but I digress.
OK. I ran my backups. So far, so good. Downloaded Movable Type Pro for Bloggers (version 4.2). Unzipped it to a temp folder.
Then, I renamed my old mt and mt-static libraries and created my new ones. (I separated and moved the new mt-static, as I had done previously.) Then, I copied over my old mt-config.cgi, as instructed.
Now, I'm supposed to 'Consult "Additional Upgrade Resources"'. Hmmmm. A hyperlink here would be nice, wouldn't it?
OK. Well, now I've opened up a file that I apparently downloaded with the 4.2 install called Readme.html. It says I need the following:
Perl 5.6.1 or greater;
A web server like Apache, or Windows IIS;
Access to a database like MySQL, SQLite or Postgres;
The following Perl modules:
* DBI
* Image::Size
* CGI::Cookie
OK. Let's see what I have here. I'm running ActivePerl 5.8.6.811, Apache 2.0.63, and MySQL 4.1.10. So, I'm guessing I'm good on all of this so far.
Now, it says the following:
Upgrading Movable Type
If you are upgrading to Movable Type 4 from a previous version, we recommend that you first back up your old installation. Then upload Movable Type 4's files over your old ones. Access Movable Type as you normally do, and you will be taken through the upgrade process.
Not really clear on all this, but basically, they're saying it will do the upgrade for me somehow, apparently. All I have to do is launch mt.cgi, I'm guessing.
But I still haven't located this mysterious "Consult "Additional Upgrade Resources"". Hmmm..
OK. Now, I'm looking at the Detailed Installation Guide under the Before You Begin section. I think I've met all of these pre-reqs.
Now, I'm looking in the same place at the Quick Start Instructions. Everything is telling me to just run mt.cgi, apparently.
OK. Finally, I found it. "Additional Upgrade Resources" was just a section further down in the same Movable Type Upgrade. Doh!
OK, So, I launch my old trusty mt.cgi, and it automagically runs a script called mt-upgrade.cgi and says "Time to Upgrade!".
Nice. So, somethings working, anyway.
Time to Upgrade!
A new version of Movable Type has been installed. We'll need to complete a few tasks to update your database.
Information about this upgrade can be found here.(broken link)
In addition, the following Movable Type components require upgrading or installation:
* Professional Pack Version 1.2
* Community Pack Version 1.6
* Widget Manager Upgrade Assistant Version 1.1
I click Begin Upgrade. It wants me to sign in. It puts in my username and password for me. Fair enough.
Upgrade complete!
Plugin 'Community Pack' installed successfully.* Upgrading database from version 3.2001.
* Upgrading table for MT::Entry::Meta records...
* Upgrading table for Job Exit Status records...
* Upgrading table for MT::Asset::Meta records...
* Upgrading table for Asset records...
* Upgrading table for Asset Placement records...
* Upgrading table for MT::Author::Meta records...
* Upgrading table for Tag records...
* Upgrading table for MT::TBPing::Meta records...
* Upgrading table for MT::Category::Meta records...
* Upgrading table for Field records...
* Upgrading table for Job Function records...
* Upgrading table for MT::Template::Meta records...
* Upgrading table for touch records...
* Upgrading table for Role records...
* Upgrading table for Object Score records...
* Upgrading table for Job Error records...
* Upgrading table for Association records...
* Upgrading table for Job records...
* Upgrading table for MT::Blog::Meta records...
* Upgrading table for Tag Placement records...
* Upgrading table for MT::Comment::Meta records...
* Upgrading table for Entry records...
* Upgrading table for Entry records...
* Upgrading table for Archive Mapping records...
* Upgrading table for User records...
* Upgrading table for User records...
* Upgrading table for TrackBack records...
* Upgrading table for Category records...
* Upgrading table for TrackBacks records...
* Upgrading table for TrackBacks records...
* Upgrading table for Template records...
* Upgrading table for Template records...
* Upgrading table for IP Ban records...
* Upgrading table for Permission records...
* Upgrading table for Permission records...
* Upgrading table for fileinfo records...
* Upgrading table for TrackBack records...
* Upgrading table for Blog records...
* Upgrading table for Comment records...
* Upgrading table for Comment records...
* Upgrading table for Contact records...
* Upgrading table for Entry records...
* Upgrading table for Category Placement records...
* Upgrading table for Session records...
* Upgrading table for User records...
* Upgrading table for TrackBack records...
* Upgrading table for Category records...
* Upgrading table for Template records...
* Upgrading table for Permission records...
* Upgrading table for fileinfo records...
* Upgrading table for Comment records...
* Upgrading table for Contact records...
* Creating new template: 'Comment Response'.
* Creating new template: 'Comment Response'.
* Creating new template: 'Userpic'.
* Creating new template: 'Commenter Notify'.
* Creating new template: 'Search'.
* Creating new template: 'New entry notification'.
* Creating new template: 'Registration Form'.
* Creating new template: 'Status Message'.
* Creating new template: 'GlobalJavaScript'.
* Creating new template: 'Footer'.
* Creating new template: 'Profile Error'.
* Creating new template: 'Registration Confirmation'.
* Creating new template: 'Commenter Confirm'.
* Creating new template: 'Login Form'.
* Creating new template: 'Simple Header'.
* Creating new template: 'Form Field'.
* Creating new template: 'Password Reset Form'.
* Creating new template: 'New Comment'.
* Creating new template: 'Profile Edit Form'.
* Creating new template: 'Registration notification'.
* Creating new template: 'Email verification'.
* Creating new template: 'Sign In'.
* Creating new template: 'Profile View'.
* Creating new template: 'New Ping'.
* Creating new template: 'Navigation'.
* Creating new template: 'Comment throttle'.
* Creating new template: 'Password Recovery'.
* Creating new template: 'Profile Feed'.
* Creating new template: 'Simple Footer'.
* Creating new template: 'Subscribe Verify'.
* Creating new template: 'Header'.
* Creating new template: 'Entry Notify'.
* Creating new template: 'Mail Footer'.
* Removing unused template maps... (100%)
* Updating system search template records...
* Classifying category records... (100%)
* Populating default file template for templatemaps... (100%)
* Migrating Nofollow plugin settings...
* Assigning junk status for TrackBacks... (100%)
* Classifying entry records... (100%)
* Updating widget template records... (100%)
* Assigning junk status for comments... (100%)
* Populating authored and published dates for entries... (100%)
* Assigning user status... (100%)
* Merging comment system templates... (100%)
* Assigning basename for categories... (100%)
* Moving metadata storage for categories...
* Moving metadata storage for categories...
* Assigning blog template set... (100%)
* Moving OpenID usernames to external_id fields... (100%)
* Removing unnecessary indexes...
* Assigning user authentication type... (100%)
* Assigning embedded flag to asset placements... (100%)
* Assigning author basename... (100%)
* Assigning blog page layout... (100%)
* Replacing file formats to use CategoryLabel tag... (100%)
* Migrating permissions to roles... (100%)
* Updating template build types... (100%)
* Assigning entry comment and TrackBack counts... (100%)
* Migrating permission records to new structure...
* Migrating role records to new structure...
* Migrating system level permissions to new structure...
* Adding new feature widget to dashboard... (100%)
* Assigning all permissions to blog administrator... (100%)
* Recover permissions of system administrators... (100%)
* Removing Dynamic Site Bootstrapper index template...
* Updating user permissions for editing tags... (100%)
* Migrating any "tag" categories to new tags... (100%)
* Setting new entry defaults for blogs... (100%)
* Database has been upgraded to version 4.0067.
* Plugin 'Professional Pack' installed successfully.
* Plugin 'Community Pack' installed successfully.Error during upgrade:
Return to Movable Type
So, I click on Return to Movable Type and it brings up what appears to be a slick new movable type home screen.
But the bottom of the screen has a nasty warning that says:
"Movable Type was unable to locate your 'mt-static' directory. Please configure the 'StaticFilePath' configuration setting in your mt-config.cgi file, and create a writable 'support' directory underneath your 'mt-static' directory."
So, I did as I was told. I added the StaticFilePath configuration setting to my mt-config.cgi, and the warning disappeared.
Hmmmm. Maybe the update worked?
I tried to preview my current post in the upgrade, and got an error message:
Publish error: Publish error in template 'Individual Entry Archive': Unknown tag found: TechnoratiTags
So, I clicked on Design - Templates. Then, under Archive Templates - Individual Entry Templates.
Sure enough, right at the top it says the following:
One or more errors were found in this template.
*
at line 83 is unrecognized.
*at line 84 is unrecognized.
*at line 1482 is unrecognized.
Hmmmm.OK. Now, I see what the problem is. My plugins are missing. I need to move them from my old mt\plugins folder to the new mt\plugins folder.
So, I'm going to copy over the following:
mt\plugins\commchallenge
mt\plugins\delicioustags-0.1
mt\plugins\technoratitags-0.3
mt\plugins\templateRefresh
I will not copy over mt\plugins\nofollow because they say the plugin is obsolete and I won't copy over mt\plugins\spamlookup because there is already a copy of it in the new install.
OK. I copied those 4 folders over. Now, following the directions for the next folder, I'm not going to copy over the following file because it's obsolete:
mt\php\plugins\init.nofollow.php
But I will copy over the following:
mt\php\plugins\function.MTCommentChallenge.php
OK. That's done. OK. Now I see the step where they tell you not to forget to upgrade/copy your old plugins. They tell you after they tell you to go ahead and run the mt.cgi. Nice. Well, better late than never, right?
http://www.movabletype.org/documentation/upgrade/
If you elected to create a fresh install of Movable Type, remember to re-install each of your plugins - Check to see if there are new versions available for any of the plugins you had installed previously. If a newer version is available, install them.
OK. Now, when I bring up my individual entry template, I don't see the error messages about unrecognized tags.
I click on Manage - Entries and bring up my last post. I click Preview, and the preview works. No errors this time. Maybe it's working?
OK. The upgraded version of MT seems to be working, but it's still very slow. It takes much too long to post entries, comments, etc. I'll see if I can get this to work faster, but this was one of my main goals in upgrading....to get MT to run faster, and I'm not there yet, obviously.
Now I noticed that my MTCommentChallenge plugin isn't functioning and I'm being overrun by spam. Great. Have to get that working again.
I attempted to post a comment and I did see that it doesn't post my little comment challenge like it used to.
http://jayallen.org/projects/comment-challenge/2006/03/download_installation_and_configuration.php
Apparently, I've lost my little MTCommentChallenge plugin tags somehow. It looks like the upgrade, for whatever reason, turned off my MTCommentChallenge settings. So, I just had to go into Tools - Plugins and edit the settings for the plugin. To turn it back on, basically. It's working now.
Update: This morning I discovered the following error/warning on my MT/Apache server.
"Windows is running low on virtual memory."
So, I rebooted it and then I saw this error:
"Perl command line interpreter encountered an error and needs to close."
That's not giving me a warm and fuzzy feeling.
So, I did a cold boot and then when it came up I didn't have any errors.
Posted by Rob Kiser on August 15, 2008 at 6:38 PM
Comments