As I had mentioned several times, I had been frustrated with Typo. Several bugs or misfeatures that really annoyed me, upgrades that had frustrated me, and sometimes the feeling that more or less visible things were broken from time to time in new releases. And while the upgrade problems were mostly because of the need to upgrade Ruby gems, still it was something that was inevitable with Typo apparently, so sticking with Typo meant having to deal with Rubygems, which as you may know I hate.
So, after the last upgrade and the frustrations that came with it, I decided to ask around for good blogging software. The main contenders I had in mind were Wordpress and Movable Type. Most of the people who replied talked wonders about Wordpress, but I decided to try both. Wordpress’ installation was ridiculously easy (I’m talking about installing my own copy, not opening a blog in wordpress.com obviously) and I had a working blog pretty quickly. Also, at least the first impression of the UI is that it’s very slick and easy to use. It shows maturity. Movable Type was easy enough to install, although I did have some problems (mostly due to my own stupidity, but still). The first impression was that Movable Type was much “heavier” and maybe a bit too much for a single, personal blog. So I decided to go for Wordpress, which was the one that I had been recommended by most people anyway.
So, the first thing I had to do was exporting the content from Typo’s HCoder so I could import into Wordpress. I quickly found some script for Typo that would export in Wordpress’ format, for easy import. It worked very well, although I did a problem with the tags: they were treated as normal categories, so I ended up with many categories and no tags (and a huge, horrible, impossible to navigate sidebar with dozens of categories). I started to look around, and I couldn’t find a spec for the wxr format. Maybe I was naive thinking that there would be one, but hey. In any case, eventually I figured out that I had to change the:
<category>rants</category>
to
<category domain="tag">rants</category>
for the tags. The categories had to stay as they were, but luckily for me, all uppercase names were categories, and all lowercase names were tags, so I could do the trick with vim with:
:%s/<category>\([a-z]\)/<category domain="tag">\1/
After that, I could import back all the content, but then I had the next hurdle: the style of the blog. I didn’t mind if the design wasn’t exactly the same, but I was used to the old one and didn’t want to change it too much, so I used the excellent Opera Dragonfly to inspect the styles of the old blog, and I slowly copied the most interesting values (colours and font sizes mostly) to the equivalent CSS classes in the Wordpress theme. I’m happy with the result, so I think I’ll leave it as it is for now.
Last, but not least, I wanted to try to keep the old URLs working. I did two things for this:
- I added some URL rewrites to keep Typo’s feed URLs working. However, the Atom ones also redirect to the RSS ones, I wonder if that’ll be a problem.
- I changed the default permalink settings in Wordpress so they matched what I had in Typo. Hopefully almost all blog posts will actually keep the URL and the migration to Wordpress won’t be very traumatic. You tell me if I’ve broken anything ;-)
One thing that I don’t like about Wordpress’ blog editor is that apparently it doesn’t allow you to write in some Wiki-like syntax, like Markdown or Textile. I know Movable Type does have it, but several other things made me stick with Wordpress and I’m happy overall. At least for now ;-)

Posts
Esteban using PHP in his site!! It’s the end of the world, prepare for 2012! :))
January 25, 2010 @ 6:27 pm
Haha, I was wondering if anyone would say anything about that ;-)
January 25, 2010 @ 6:47 pm
As I read through your Typo rants, I have to agree.
I jumped on the Ruby/Typo bandwagon a few years ago since I needed a trivial, personal, blog that used SQLite and was interested in Ruby. I was coming from WebAPP. Well, as you know, Typo uses Ruby on Rails and all the requirements that entails. It is not light weight in server resources, requiring over 512MB of RAM just to update Ruby Gems. In fact, I’ve had `gem update` lockup with 512MB and had to upped the RAM to 768MB just to get it to complete. That isn’t a problem for a home-hosted server running in a VM, but at a hosting provider, that change almost doubles the monthly cost. I also ended up running pound as a front end to Mongrel running 3 instances since requests were taking too much time.
I’ve noticed that Typo RSS feeds broke sometime around 1/1/10. I also missed some of the other features that disappeared rather than being disabled by default. I can appreciate that some users had problems with them, but I didn’t so why remove them completely?
After seeing the results of your migration, I’m convinced and will be migrating within the next month. My dislike of PHP is great. I’ll be going with MT in my first migration attempt and may drop back to WP if that fails. I know perl.
If these are too complex, I’ll just go with Joomla or Drupal which will be helpful in my day job.
For the most part, I’ll miss Typo. There are many excellent things about it. I just wish it had better regression testing built into the release process.
For anyone seeking Typo help, the IRC support room is fantastic. Every time I’ve asked a question, it was answered accurately and quickly.
February 23, 2010 @ 10:00 pm
John,
Thanks for your comment! I also dislike PHP, but figured that I wasn’t going to touch the code so I’d be fine. Movable Type looked good, but too complex for my needs. Not that I couldn’t use it or anything, but Wordpress seemed to do everything I needed with a much more “focused” UI. If you really prefer using a Perl-based system, you’ll most probably be just fine with MT.
February 28, 2010 @ 5:11 pm