I've upgraded to Movable Type 3.2. One of the first things I did after upgrading is to use the new archive basename feature for the individual archive filenames. Immediately, though, I found that editing an entry caused the basename to change by adding a "_1" to the end.
Now, this is normally done to prevent collisions, but an entry should not cause a collision with itself. I did some searching and found that this is a known defect in Movable Type and can be avoided by using the save button on the entry edit screen rather than the one on the preview screen.
I will say the anti-spam filtering for comments and trackbacks is wonderful. They come enabled by default and have been already filtered out hundreds of junk trackbacks that my blog has received in the last few days.
Next, I intend on creating a new site identity. I already have all of my templates and other site specific artifacts in a Subversion repository. I now have to begin editing those templates and other things and come up with a nice clean design with cool CSS tabs for navigaion.
