Seems a lot of people are having troubles upgrading to MovableType Version 3.2, and I must admit when I went to read the upgrade instructions I was totally confused. I have yet to find the page that talks about what changes need to be made to templates.
Being I have a very customized site, I have concluded I am going to have to setup a test site to do the upgrade on. If you read the SixApart user forums their are a lot of people asking for help on various issues, and it looks like users are helping users and their is very few staff replies to problems.
When I see messages that indicate all comments and category information are being deleted not mention hung upgrades I wonder if SixApart attempt to automate upgrades is not as slick as they are advertising.
My advice is to sit on the fence a few days as I am sure their will be some updates coming soon.
To be clear, you can upgrade to 3.2 without touching any of your templates or making any changes. And people who’s upgrades are hanging are generally as a result of not having the requisite javascript files in the right place (the mt-static directory). So it is really pretty painless, though we need to make the upgrade documentation clearer and will be doing so today.
I upgraded one of MT installations without a hitch. But I decided to take advantage of the opportunity to build a new design for the weblog I intend to use it with. So I did an entry export/import. I would think you would want to be very careful with the complexity of your site.