Upgrade to MovableType 4.1 Complete

| | Comments (6)

The code and design for this site have pretty stagnant for the last two years. Everything was functional, but the design was old and needed some serious improvement. With the recent release of MovableType 4.1, I decided to put some time into this and get it upgraded.

Many hours later, it's done! I spent lots of time on this -- probably too much -- but wanted to come up with a clean upgrade process.

To back up a step and look at what I was trying to achieve, these were my goals for the upgrade:

  1. Create a more useful template for individual articles. The vast majority of visitors come from search engines or referrals and land on an individual article. My old individual article page was very simple and didn't provide any links to other parts of the website.
  2. Make comments useful again. I haven't touched the comment forms in a couple years and they've fallen far behind today's best practices for letting real visitors leave comments while keeping the spammers away.
  3. Find or create a better visual design. By catching up with the latest MT templates, I should be able to find and/or modify a more interesting visual design for the site.

Because I decided to replace all of my existing templates with the latest ones shipped with MovableType, my upgrade process was a little trickier than previous upgrades. Some of the key points with the upgrade were:

  • Retain all existing articles/posts with the same URL scheme
  • Retain RSS & Atom feeds at the same URLs, but with updated templates
  • Keep the same archiving formats (by category and by month)
  • Refresh all templates to use the standard MT 4.1 set
  • Remove obsolete plugins

With the above goals and key points in mind, and after lots of experimentation, I came up with the following upgrade process:

  1. Install XAMPP and Movable Type 4.1 locally on Windows (steps)
  2. Clone MT database from live server to local system
  3. Upgrade local to MT 4.1, refresh all templates, then tweak to get everything right
  4. Install MT 4.1 on server
  5. Migrate database back to live server and publish

Of these, step #3 took the vast majority of the time, but the good news is I was able to play with everything locally without disrupting the live site.

6 Comments

I think you should upgrade to wordpress as its better then MT, Just give it a try and let me know if u find it good.

Let me know if you need anyhelp.

Its just a suggestion as i want you to know what is better.

A regular visitor of your website

Robert.

Kudos to you. I know how big of a nightmare it can be when upgrading plus having to edit a new template to your linking. However I do recommend wordpress as you wouldn't even have to worry about reconfiguring your archive settings like in MT.

I just followed all of your steps - whew! Thanks for the post.

Thank you for your work--this has worked out well for me--Thanks for sharing--Andy

I liked this post but as others have said, WP is probably the better platform for this kind of work.

Thanks all wordpress fans for your suggestions to switch. I'm sticking with movable type for now. In any case, it's good diversity to have multiple popular blogging platforms.

Leave a comment

About

This is the personal website of Brian Cantoni. All opinions on this site are my own.

Contact email: brian at cantoni.org

Day job: Yahoo! Developer Network

Ligit Search

Creative Commons License
This weblog is licensed under a Creative Commons License.