Movable Type vs WordPress
About two years ago, I installed Mephisto and started blogging. I chose Mephisto mainly because it was written in Ruby, one of my favorite programming languages. However, I soon realized I was better off using the best tool for writing instead of caring so much about which language the tool was written in.
So I moved from Mephisto to Movable Type and was very happy with the switch. For a while anyway. Recently, there were several things about Movable Type that started to really bother me.
- Manual upgrades were annoying as they seemed to take a lot of time, and I occasionally broke things during the process.
- I never figured out how to install my own themes. My site looked bland for a long time while I waited for better default themes.
- I couldn’t figure out plugins either. I wanted to customize the sidebar of my site, so I ended up spending a lot time changing the theme by hand. After that, I couldn’t switch themes without losing all my work.
- Publishing static content just took too long. My site loaded quickly because of it, but I wanted something that wasn’t so annoying to me.
- I tried switching to dynamic publishing, but it didn’t work very well. It may have been my web hosting company, but I really like them and don’t want to switch.
My first thought was to try the hosted version of Movable Type over at TypePad. I’d never have to do an upgrade, and I assume the included themes are much nicer. However I decided that $9 a month is more than I wanted to pay to use my own domain.
Several of my friends and family use Blogger, which is free, so it seemed a good place to try next. Blogger only includes a few default themes, but adding your own is easy. It feels like thousands of custom themes are available, though I would have to install and maintain them myself.
Blogger does not support uploading PDF or MP3 files, which isn’t convenient, but I probably could have hosted them elsewhere without too much trouble. I also would have lost the ability to have a static page for our family newsletters. But the biggest issue was email. I couldn’t use my own domain unless I switched to Google Apps for email.
WordPress provides free hosted blogging accounts, so I thought I’d give it a shot next. I got quite far along the road to satisfaction. MP3 files were still evil, but PDF files were okay. $10 to use my own domain seemed reasonable. I found a theme I liked, and there was enough built-in functionality to get my sidebar set up how I wanted.
The biggest win was not worrying about upgrades or performance. WordPress would even import a blog exported by Movable Type. Awesome. Except I’d written everything in Markdown format, which wasn’t supported.
The WordPress guys said Markdown was more demanding on their systems, which sounded fair enough. So I had some fun writing a script to convert my Markdown-formatted blog entries to HTML. During the process, I found several broken links, which I was glad to fix.
But I found that writing HTML takes longer than writing Markdown. Not surprising really. It’s why John Gruber created it in the first place. Then I discovered that embedding YouTube videos required using some proprietary format. And then I realized they had the same email problem that haunted Blogger. I don’t want to switch to Google Apps. Please just add email forwarding as a paid upgrade.
I wasn’t happy. But after reading a bit more, I stumbled across the fact that the WordPress software could update itself. Interesting. I decided to try installing it myself.
Installing themes and plugins turned out to be fairly easy — unzip a theme into the themes directory, then select it on the Themes page; unzip a plugin into the plugins directory, then activate it on the Plugins page. Wash, rinse, repeat. Some of the plugins put their configuration pages into odd locations, but I was able to track everything down. And once I’d set up a widget in my sidebar, I could change themes without losing anything. It just worked.
Well, mostly. WordPress says it supports installing and updating plugins from within the software itself, which would be awesome, except that I couldn’t get that to work. Manual installation was easier. I sigh and shake my head whenever I think about it.
2009-01-21: I got automatic plugin installs to work by following these instructions (member’s only) on NearlyFreeSpeech’s forums:
- First I created a folder at the root of my site called “tmp” (for me, it was /home/public/tmp).
- Then I added this line to my WordPress configuration file:
The problem is that WordPress tries to download stuff to a temp folder before moving it to its final destination, but the system settings had the wrong temp folder listed. Since I’m running with PHP’s safe mode on, WordPress couldn’t read or write to the temp folder, causing the whole thing to fail.
It’d be nice if WordPress added a “Temp Folder Location” setting to their configuration options or just downloaded stuff directly to its destination if the temp folder is inaccessible.
I’m happier now that I can install, update and remove plugins, as well as update WordPress itself, all from within WordPress.
Here are the plugins I’m using right now.
- Automatic Timezone because WordPress is too lame to figure this out on its own.
- Google Analyticator adds the Google Analytics tracking code.
- Simple Google Sitemap automatically creates my sitemap.
- KB Robots.txt allows me to add my sitemap to my robots.txt file.
- Markdown (of course :-))
- Recently Popular highlights what people are reading on my site.
- Twitter lets you know exactly what I’m up to at all times. You do want to know this, right?
- Yet Another Related Posts Plugin works great and requires no work at all.
- Next of Kin isn’t activated yet, but I’m thinking about it.
- All in One Adsense and YPN handles the ads on my site.
- FD Feedburner Plugin lets me use FeedBurner for my feeds.
I tried these out, but stopped using them pretty quickly.
WordPress.com Statswas annoying because it required me to login to my WordPress.com account every time, which didn’t work reliably. The reports and statistics were pretty good when I could get it to work. Redirectionhas a feature where it monitors post and category URL changes and automatically starts redirecting visitors. However, when I deleted a category, it created an endless redirection loop that took down my entire site. Other than that, it worked pretty well at helping me figure out and solve problems with missing pages.
I recently noticed two more things about WordPress that I really like.
- A word count is always visible when I’m writing. I’m happy the final version of this article is a few hundred words shorter than the original.
- My comments are automatically highlighted in a different color, which makes it easy for readers to find my replies. Not that you’d miss me in a list of three comments.
There are a couple of things I don’t like about WordPress.
- Maybe I’m just used to Movable Type’s static publishing, but I’m not sure that’s a valid excuse for WordPress to be slow. Luckily, there are caching plugins that should help a lot. I find I prefer cached dynamic content over pre-published static pages. At first, it didn’t seem to matter, but one is handled for you behind the scenes while the other is constantly in your face. It may be a personal preference, but it makes a difference to me.
- The media library is pretty lousy. You can’t rename files, though you can delete and re-upload the file with a new name. I have to be extremely careful when uploading files.
Overall, I’m very happy with WordPress. There is lots of good, very little bad, and no ugly. The hardest part was trying out similar plugins and picking the best ones to keep.