Migrating from Radio Userland to WordPress

Well, I’ve done it! Regular readers will notice that, after nearly 4 years, Status-Q has a new look. Actually, this is temporary and there’s lots of tweaking to be done yet. It’ll soon look a bit more like its old self.

But the underlying reason for it is that Status-Q is no longer produced using the Radio Userland software package, but with the very nice new web-based WordPress. Setting up and running WordPress was easy. Importing all my old posts and trying to make sure that all my old URLs still worked was rather more challenging. I’ve been writing up the process on the WordPress wiki in the hope that it may be of use to future pilgrims following the same trail.

So why the change? Well, Radio Userland was a wonderful program in many ways. As a combination of scripting engine, database, webserver, outliner, RSS viewer with a nice front-end, it was pretty revolutionary in its day and you could do some very cute things with it. It also had the advantage that you could write as much as you liked while disconnected and then upstream to your server when you were next online. All very cool.

However, when it went wrong, which it seemed to do from time to time for absolutely no reason, it was a devil of a thing to debug. The documentation was impossible to find, the scripting language and error messages often rather unhelpful, and since Dave Winer departed from Userland Software there doesn’t seem to have been much active development on it. And I could count the times that working offline has been important to me on the fingers of, well, no hands.

So I’ve been meaning to move to something else for some time, but the task of converting my past posts and keeping my URLs intact seemed pretty daunting. I’d looked at doing it with Movable Type and it appeared that a lot of manual editing would be involved. When Radio died again just over a week ago, though, it gave me the incentive to go and find out just how difficult it would be with WordPress, and the answer was, with a bit of hacking, not too hard at all. So here I am! Let’s see how it goes…


Thank you very much for writing the directions on the wiki, that’s very helpful.

Well, I fully agree with your comment. 🙂

BTW: I visited your blog earlier today and I just wanted to congratulate you on a well presented, and informative resource.

It’s not often that I come across a web site that offers a wealth of quality. 🙂

I’ve kept using not only Radio, but also the weblogs.com server, which is going to be discontinued. I’m flirting with the idea of migrating to Word Press, but your wiki entry is gone. Is there a copy elsewhere. (I’ve retrieved one through archive.org, but worried it may not be the latest.)

Another Radio user departs
I have become oddly fond of the quirky Radio Userland software, so I always feel a twinge when I read reports from savvy users who are switching to other blogging platforms, as seems to happen fairly often: Radio was a great program – I used it for four y

Got Something To Say:

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax


© Copyright Quentin Stafford-Fraser