As a few of you know, we've been trying to switch from Blogger to MovableType. I waited until MT 3.0 was released and purchased it. Then, since I don't know diddly squat about CGI scripts, I chose to go with a paid installation by the Movable Type crew.

That was about 3 weeks ago. There was quickly a hitch in that an error message was being generated which seemed to have the installer stumped. She said she checked with the crew who wrote the program for MT 3.0 and they didn't know what to make of it either. So, I tried to get our domain host to help out with it. Turns out they don't offer support for installed scripts. I've been going round and round with the Movable Type installer for the last three weeks trying to do whatever I could to facilitate fixing the problem.

I finally gained access to my CGI error log and passed that on to the MT installer. She says that it's no help and that it looks like we'll have to make do with the older MT 2.66 weblog program since it installed without any problems.

Out of frustration I decided that I had nothing to lose and did a Google search using "CGI, errors" as the search criteria. The very first hit that I opened was on debugging common CGI errors. The friggin' second most common CGI error listed and the second most common cause of that error was friggin' exactly the error message that the Movable Type programmers supposedly were stumped by! Mind you we are paying Movable Type to install this program. This wasn't some favor they decided to do for us. And I, the guy who doesn't know jack about CGI scripts, find the problem and the fix listed on the open web within literally 30 seconds of looking!?!

I'm still convinced that the Movable Type platform is superior in virtually every way to the free Blogger one we've been using. But, it would be an understatement to say that I'm disappointed in the competence exhibited by the "professional" (by definition since we're paying them for the install) folks at Movable Type.