January 14, 2004
Upgrading to Movable Type 2.65
One of the last things that I did before throwing the new site design out into the open was to upgrade Movable Type version 2.64 to 2.65. The changes made to 2.64 are listed in the Guide to new features in MT 2.6, but the main reason for doing this was security issues. Anyway, here’s the steps that I took to carry out the upgrade, along with a few notes on what’s actually changed.
As stated within Movable Type’s upgrade instructions, it’s a good idea to back up your weblog first - just in case! Then it’s time to download the 2.65 upgrade.
- I ran a comparison between the files from version 2.64 and 2.65, and here’s what I uploaded/upgraded:
mt-send-entry.cgi- upgrade\docs\(contents of directory) - upgrade\lib\MT.pm- upgrade NOTE: it only upgrades the Movable Type version number!\lib\MT\ConfigMgr.pm- upgrade NOTE: it adds the line$mgr->define('IgnoreISOTimezones', Default => 0);to the file\lib\MT\default-templates.pl- upgrade\lib\MT\XMLRPCServer.pm- upgrade NOTE: I did NOT upgrade this file as I’d already added the new file - this file should generally be upgraded, however, as it is a security issue!\lib\MT\Template\Context.pm- upgrade
- Downloaded the previously installed versions of the files shown above (except for
docs\) from my server installation - as with backing up the weblog itself, it gives you a way back if anything goes wrong!! - Uploaded the new files to the relevant directories. As stated within Movable Type’s upgrade document, ensure that all non-image files are uploaded in ASCII mode, AND, ensure that
.cgifile permissions are set to 755, and,.pmand.plfile permissions are set to 644. - Accessed my Movable Type login screen and noticed that the copyright line at bottom of the page now correctly stated version 2.65. I then logged in successfully.
- Issued the ‘Rebuild Site’ command
Now, on visiting my weblog page, the Movable Type version is listed as 2.65, and the entire weblog performs as before - a successful upgrade without any trouble!!
