I've been fairly happy with Movable Type, but the upgrade to 3.2 has been a disappointment, a discouragement, and enormously frustrating. I forgave SixApart for the clunky manual install process when I tried it the first time (version 2.x). Once installed life was good. And then I purchased a license when they went to the 3.1x series. I thought the 2.x -> 3.1x upgrade was pretty convoluted when I did it then. Download, but be careful how you ftp, copy files over the other ones (always a learning experience in Unix to do this correctly), and then verify and monkey with the permission settings. Yikes! But I did it, and promptly forgot about it. The blog was functioning. I picked up using Ecto as my blogging client and life was great.
[LESSON 1: take notes when doing installs. Really. Take notes.]
And then the upgrade just hung until, saved by the excellent SixApart e-mail support, I was reminded of how the ".js" files need to ftp-ed in ASCII mode not binary. Well I've been avoiding ftp and using scp instead, which seems easier and used ssh. Anyway, scp doesn't work for this. I needed to upload the ".js" files again and install and set permissions (do they need to be executable? I should know, but ...).
So, I did get it running. But now, when I've tried to use Ecto to create a new post on a new weblog I get posting errors. Yeah, could be an Ecto error, but, right now it's just one more headache. It's been two whole days ....
I think MT is reaching a complexity stage that's unsustainable. I think I'll be looking for alternatives. But I'm not sanguine that the grass will be greener anywhere else. I think we're in for a long experience of learning about systems and complexity the hard way.