A Faster Upgrade to Movable Type 3.16


Published on April 19, 2005 at 12:35 PM EST
Last updated on October 9, 2006 at 12:02 AM EST
In the Tutorials category.

An upgrade to Movable Type 3.16 can be done a little quicker: by checking file dates, it appears that uploading just the following will perform the upgrade from version 3.15: docs/ examples/ (though you really don’t need this.) lib/ php/…

An upgrade to Movable Type 3.16 can be done a little quicker: by checking file dates, it appears that uploading just the following will perform the upgrade from version 3.15:

  • docs/
  • examples/ (though you really don’t need this.)
  • lib/
  • php/
  • plugins/ (containing the “nofollow” plugin, which I recommend against using.)
  • schemas/
  • search_templates/ (though if you’ve customized your search template, don’t upload these.)
  • tmpl/
  • tools/
  • all root files (mt.cgi, mt-comments.cgi, etc.), except the mt-upgrade files. Don’t forget to set 755 permissions on the cgis.

Of course, docs/ and mt.js go in your “static” directory. Everything else goes in the cgi-bin.

Ok, so it’s not much quicker than just uploading everything, but every second counts, right?

This article is tagged as: MTUpgrade, Tutorials

If you found this article useful, please consider supporting this site through a donation.

Comments

So far, there are 2 comments and Trackbacks on this entry. Add yours!

1

I am wondering why you don’t run the mt-upgrade script to update the schema of the database. Is that not important?

2

If upgrading from 3.1x to 3.16, no, mt-upgrade.cgi shouldn’t be run because nothing needs updating. Refer to the Movable Type Upgrading Instructions.

Post a comment

 
 
 


TrackBack URL for A Faster Upgrade to Movable Type 3.16:
http://www.eatdrinksleepmovabletype.com/cgi-bin/mt/mt-tb.cgi/270