Harrowing MT upgrade

So the Red Sox managed to pull out a win in Game Five, and I was in a good mood. Then I went upstairs to complete my upgrade to Movable Type 3.1, and in the process I became convinced that I had completely hosed my entire site and database. Then I was in a bad mood. In fact, I was very nearly frantic, and it was in this state of near despair that I decided I really needed to read the directions very very carefully. For those of you following along from home, here is the important passage:

“If you are upgrading from version 2.6, 2.61, 2.62, 2.63, 2.64, 2.65, 2.66 or 2.661: Run mt-upgrade30.cgi, then mt-upgrade31.cgi.”

It did NOT go on to say that “if you don’t do this, you will become wedged in a most horrifying and spectacularly nonlinear fashion and your account will seem to vanish until you jolly well go back and get it right, you enormous butthead.” I may suggest they add this passage to the documentation for sensible though occasionally impatient folk like me. Good night.

3 thoughts on “Harrowing MT upgrade”

  1. Whew, glad you got it back! I haven’t upgraded specifically because I haven’t had time to sit down and read this carefully; am worried I’d do exactly what you did, or worse.

  2. To execute a cgi-script, chmod it to be executable first. I remembered this for the MT upgrade, but then forgot about it for the MT-BlackList upgrade. This made my server return some generic error-message when trying to run the MTB-upgrade script, which had me worried for a while since Jay’s out this week, and I didn’t want to leave my blog wide open to comment and trackback spam for a week.

Comments are closed.