Warning: MoveableType techno-rant ahead…
Lately, every time I save a new post I get an “Internal Server Error” message from MoveableType. The error in my server log reads: “Premature end of script headers: /var/www/html/mt/mt.cgi”. After a lot of Googling I found a mention somewhere (can’t seem to find it right now) that indicated SmartyPants might be the culprit.
SmartyPants is a MT plug-in I use, which converts straight-and-boring quotes (“) to typographically-correct curly, or smart, quotes “like so.” I removed SmartyPants, grudgingly, as I like to be typographically correct, and the problem disappeared, for a while. Now it is back.
Unfortunately, because I had set “Markdown + SmartyPants” as my default text format, when I re-rendered my site, all my postings reverted to the “None” formatting option. Blech. Worse — all my RSS feeds were updated, with raw, unprocessed [Markdown] code in them. My apologies to everyone who may have seen a “flowdelic” update in their RSS readers, only to find a bunch of old posts, but stripped of formatting.
So last weekend I planned to take a crack at learning the MT template language and finally customizing my templates. But instead, I spent my time tracking down Internal Server Errors. Sorry kids.
All is not lost however, I think I have found my solution — WordPress. WordPress is open-source blogging software that has gotten a lot of recognition of late, and it has typographical-correctness built in! The fact that it is written in PHP is appealing too, as I am much more comfortable with PHP than Perl.
So rather than investing in wrestling with/learning MT when it looks like many are leaving in the wake of the new MT 3.0 licensing brouhaha, I’ll be trying my hand at WordPress this weekend. Wish me luck!
One thought on “Goodbye MT, Hello WordPress”
You’ve seen the light… no more wacky errors for now reason and no more rebuilding!
WordPress rocks… been very happy since I made my move. Importing takes about 30 secs and you just move on…