MT 4.2

I just bussed in all of the upgrade files for Movable Type 4.2, so I had to
hustle together an entry to see whether it lives up to the
hoopla,
especially the faster page-creation times, which had become downright arthritic
with the latest releases (e.g., 4.x).

So far, I can offer the following (exclamation-style, so as to keep
with the mood of 4.2’s release):

  • the upgrade was a cinch. That’s good!
  • my search form is broken. That’s bad!
  • the basic templates held up. That’s good!
  • I will have to install a dummy blog and ransack its templates to
    troubleshoot the search error, and I have no time for that. That’s
    bad!
  • a full site rebuild took less then seven minutes. Good!
  • posting this entry took something like four seconds. Faster than before!

I still haven’t read any of the release materials closely enough to figure
out the difference between MT 4.2 and MT Pro. For now, my justification is
not only a case of the late-summer lazies, but also a principled objection to
the "Pro" designation, which, for my purposes, would be better if it were "Am"
or, on the best of days, "Pro-Am."

Up- or Down- A Grade is a Slope

It was upgrade weekend for the blog, meaning I had my eyes turned under the
hood and my fingers in the blog code Friday into Saturday (today, all reading,
responding, and figuring grades).

I was running MT3.2, growing every day more envious of those who were putting
to use the tagging features built into 3.3+. The upgrade was a cinch.
Just FTPed the files into place and logged in. The config file didn’t need
any changes. Well, it didn’t require any changes, that is, until I also
converted the database from MySQL4 to MySQL5. For that, I had to add a
DBSocket line to the config file. I had not a clue about it at the time,
but the support folks at icdsoft.com are remarkably good.

That’s a hearty new cumulus tagcloud over at the left. There’s a lot to
be said for MT’s tagging features built into the latest versions. Now I can merge
tags across the entire weblog, sort by tags (for editing or adding new companion
tags), and grade the tags with a max="x" setting. That’s the statement I use
to come up with ten levels for the tag cloud. And I’ve set the CSS to
display:none for the bottom five (#6-10). That way only the top five levels show
up, and the cloud isn’t the size of Lake Michigan.

Continue reading →