Converting posts from Blojsom/WordPress to Moveabletype

I had to write this because for weeks now I’ve been trying to convert blog entries between different blogging services.

The first one was converting Blojsom to WordPress, but this wasn’t too bad because both work around the RSS 2.0 format. Getting the comments, tags, metadata out and into the rss 2.0 feed was a real pain and I’m convinced I dropped a load of trackbacks and pingbacks in the process. This is another reason why I started using Disqus for all my comments.

The harder task was moving blog entries from WordPress to MoveableType. Yes I expect most of you are wondering why I would move from a far superior system to something which most people left in the dirt ages ago. Well unfortunately we still use MT on the platform and that means as backstage moves to the official blog platform, some mug had to find a way to down convert to MT 4.1 which only imports/exports in this crazy text only format.

So after lots of looking around, I finally found a XSL which I modified to do the job from a stripped down WordPress WXR file (RSS2.0 with lots of WP namespaces stuff). Its important that you strip down the WXR file as it might not be valid XML, so no XSL transform is going to work. I also took a bit of time to write a XSL to remove most of the namespaces elements or convert them into a more valid RSS 2.0 element. You can do the same with lots of finds and replaces, so I won’t post the simple XSL.

Hopefully this will save others a lot of time in the future, if your faced with the same problem.

Hello 2010, welcome to the new blog


So I finally decided to switch my blog to wordpress and on top of that I was able to install storytlr open source.

I’m still in the process of doing all the redirects and general cleaning up but its coming together quite nicely. Once its all stable I’m hoping to spend some time sorting out the styles and themes.

Getting the entries out of Blojsom was easy as pie but then converting them into a format which WordPress wouldn’t barf on was a big problem. In the end I wrote a throw away XSL to do it, because it WordPress didn’t like namespaced elements or generally anything over the standard RSS 2.0 elements. I did manage to push over the Categories and Tags but had to split them apart in WordPress later.

My whole thing is hosted with GoDaddy on their new European Servers and will be quite slow while it caches all requests.

I love Blojsom but I never upgraded to version 3.x which required a database to work. With the need for a database, it meant the ground between WordPress and blojsom was a less so. Then add cheap hosting, amazing plugins, themes and community. And its pretty much a no brainer. I also found that less and less blog editors are supporting Blojsom (some kind of metaweblog xmlrpc category issue). So now I’m able to use Bilbo which is a KDE editor with support for pretty much everything WordPress allows. I’m also able to use Google Gears which is useful when offline.

This was also a chance to get a little more serious about my blogging and footprint online. Hence I’m really hoping to stretch what storytlr can do for me and some of the projects I have for it.

In the meantime, let me know if you see anything very weird which I may have missed….

MT? you might as well be dead to me

From Fowa, do you trust these people?

I've heard about the problems but have not publiclly said much. But I'm sorry as far as I'm concerned, I stopped recommending Movable Type a long time ago and can't understand why people still use it. Suw's post on strange attractor is simply awesome and well worth reading if you also recieved the email from Sixapart. But generally it doesn't scale effectively, and I'm not saying many blogging servers do. But I wonder why everyone seems to think there are only 2 blogging application servers out there?

What about Blojsom, Community Server, Dasblog, B2, Roller, etc. Theres much more to blogging servers that MT and WordPress. Go Explorer, don't be constrained by whats the norm. Thom Shannon recommended

Comments [Comments]
Trackbacks [0]

Adams Geoblogging Blojsom mashup

My new Geo update for Blojsom

Adam has pimped out his blojsom blog with a Googlemap as a selectable flavor. I got to say this is awesome stuff and I look forward to what he does next. This also shows how powerful Blojsom is as a platform for advance blogging (geoblogging, semantic blogging, etc). I just don't understand why more people don't use it. I think Adam has also pushed me into finally buying Ecto after trying out Live Writer again. I really need to make putting in Microformats and other metadata into blog entries a lot easier for myself. That also reminds me I need to get my Blojsom 3.0 blog up and going.

Comments [Comments]
Trackbacks [0]

Blojsom 3.0 adds database storage and a even stronger API

My favorate blogging server Blojsom is shifting to Database storage for its next version. David Czarnecki the owner of the Open Source project outlined its very active history.

  • 01/29/2003 – blojsom project was registered on SourceForge and development was started.
  • 02/02/2003 – blojsom 1.0 was officially released. 18 releases were made in the 1.x cycle.
  • 09/10/2003 – blojsom 2.0 was officially released.
  • 06/28/2004 – Apple officially announces Tiger Server wherein blojsom is bundled as Weblog Server.
  • 03/14/2006 – blojsom 2.30 was officially released. 30 releases have been made in the 2.x cycle.

I remember running Blojsom betas, I think I started at Blojsom 0.7 when it could only handle one blog at a time. Then Blojsom 2.x came around and gave the whole project a real boost because it could easily handle many blogs under one install. I think the record is still 25,000 by some university in Australia. During the 1.x life of Blojsom, lots of plugins were developed and Blojsom was seriously deconstructed by the guys at HP research labs as part of there semantic blogging project. Its one of the things which I loved about Blojsom. Its nod towards something bigger than just simply blogging. Jon Udell did a talk about controlling our own data at Etech recently and one of snippits I heard was about he would run Xpath searches over his blog to pull out certain things. Its a step beyond tagging but one of the things which Blojsom has had for quite some time (Q3 2003 actually). Blojsom also has some other great stuff going for it like LDAP support!

Anyway, its a awesome blogging server and I believe Blojsom 3.0 will be better than Word Press. Its outgrown its roots in Bloxsom, which I believe is now struggling to stay around? And out grown all the Java solutions like Roller and Snipsnap. Being Java based will keep it out of the mainstream because most people have a LAMP setup on there hoster, but otherwise Blojsom 3.0 would be a bigger deal. Anyway more details about Blojsom 3.0

The first major change has been in the way blojsom is “wired” together. I've rewritten blojsom to use Spring for its dependency injection and bean management. There were aspects of the blojsom 2.x codebase that were more “patchwork” with respect to how certain components used or referenced other components.

The second major change has been in the datastore. I don't necessarily think I've exhausted all that can be done using the filesystem as a content database, but I've been feeling like there's a lot of development energy into making relations between data in the filesystem that can be expressed very easy using a relational database.

In blojsom 3.0, I've settled on using a relational database for the datastore. I'm using Hibernate as the ORM library to manage the data. This means goodbye to all the .properties files for configuration! It was fun while it lasted. The templates and themes are still stored on the filesystem, but I'd envision also storing the template data within the database as well. I've already prototyped use of the Velocity database template loader. I imagine removing any filesystem dependency will allow blojsom to be used in a clustered environment more easily.

Ultimately I think this will allow blojsom to scale much more than I think it can using the filesystem as a content database. I don't believe there are any esoteric relationships among the data in blojsom as to require a full-time DBA to manage an installation of blojsom.

The last major change has been in evolving blojsom's API.

For awhile now there are aspects of the API that were a throwback to needing certain data or referring to elements a certain way. I just wanted a more self-documenting and less redundant API.

For example, I've renamed the BlojsomPlugin interface to Plugin. I felt that having the org.blojsom.plugin package was declarative enough, but that keeping BlojsomPlugin was too redundant. None of the APIs have gone away, they're just more simple and straightforward.

The long and short of it is that you can do all of the things in blojsom 3.0 that were done in previous releases of blojsom. There are a few more components and plugins to migrate to 3.0, but I'm happy with how far things have come in such a short time given the scope of the changes.

You're more than welcome to start playing with blojsom 3.0 right now. All that you need to do after setting up your database is to add a blog and a user for that blog and you'll be able to login through the administration console.

If any of this interests you, feel free to participate on the blojsom-developers mailing list.

Being hosted with, it would be wrong for me to not to choose PostgreSQL for my database backend. I would love to try other storage backends like a XMLDB but I can't quite experiment with this blog till I've tested it fully. Maybe there will be a way to run one blog on a Database and another on a filesystem or XML Database? Because that would be great. If worst comes to worst I will just run another copy of Blojsom for testing purposes.

Comments [Comments]
Trackbacks [0]

Microformating ID

Doc Searls posted a entry about Jeremy Miller's MicroID proposal. Its a Microformat as such which allows anyone to claim verifiable ownership of content they generate. You simply hash a communication ID like a email and then hash a URI of where the content will be published. Then hash the two together to generate your unique MicroID. Don't worry theres a generator on the MicroID site.

MicroID = sha1_hex( sha1_hex( “” ) + sha1_hex( “” ) );

The important thing to remember is that MicroID is just a way to claim ownership not a authentication. Its also very simple to add anywhere. One of the examples is to put the MicroID in your meta, which I have just done. You can also stick the Microid in a div tag using the class attribute. I'm not so keen on this method, I think semanticly it would be better if it was attached in the id attribute. But I guess it would break if you had more than piece of content from the same author in the page.

I do like the idea of generating a MicroID for every comment which gets published to a blog. Maybe this is one for the Blojsom groups.

Comments [Comments]
Trackbacks [0]

Geek and Geekhag podcast number five – Tesco too big for its boots?

My and Sarah's five podcasts now available online. Enjoy and please leave a comment if you've enjoyed it or simply hate it.

This time we talk about joint/partner websites, Sarah says sorry to Blojsom creator and how Tesco is becoming Walmart in the UK and it would seem trying to beat Walmart at its only game in America with Tesco Metro's (starbucks style?).

Comments [Comments]
Trackbacks [0]

Geek and Geekhag podcast number four – Mum its about the White boxes

My and Sarah's four podcasts now available online. Enjoy and please leave a comment if you've enjoyed it or simply hate it.

British geek and his American geekhag wife talk about geeky stuff like explaining podcasting to your mum, online identity, owning your personal online data, Blojsom for dummies, folksonomy.

Comments [Comments]
Trackbacks [0]

Moving again

For quite sometime I've been having issues with running Blojsom on a shared Java host. See its possible but not ideal. It would seem Blojsom is best placed in a dedcated servlet container where it can have room to move. So for quite some time I've been holding on to my very cheap shared hosting by Interadvantage. The System Admistrator has been helping me out for quite some time but it just seems is just generally growing in popularity and outgrowing its small plot of internet land. For the last 2 months I've been trying to cut down on system hit by using OSCache and Log4j to solve the errors I might be getting. But it came to a head just recently… here's a slightly edited email I recieved.

I've noticed that whenever your site gets hit hard, our server's load goes way up and other sites become unresponsive. This is particularly a problem in the mornings, from about 8 – 12 AM our time. I assume all the geeks over here who are addicted to your blog get their RSS feed (because you get a lot of RSS traffic then), and then go hit your blog if they see something of interest.

I also took a look at your stats, and about 25% of your page loads come from

At any rate, your site is successful, and active, and it depends on Blojsom. When it's getting hit, your site dominates a loaded Dual Xeon server, so I think it's unlikely we can reduce the load to an adequate level just by tweaking Blojsom. Sadly, I again need to encourage you to look for another host. I don't think it's fair for you to try and host your blog in a shared environment; I really think you should put it on a VPS or dedicated server so that Blojsom can't hog CPU and memory that is being shared by other sites.

This came to a head this morning because our company president was trying to do something on your server at 10:00 AM, and he was very upset by the performance. He wants resolution to this situation, and suggested we give you 30 days to find a different host.

It has been fun working with you, and I'm sorry to write this note. I do wish you the best in your future endeavors.


interAdvantage Administrator

So once again I'm on the look out for a good java hoster which provide virtual private servers for people on tight budgets. So far the cheapest I've found is's private tomcat at 14.95 candian dollars a month for Tomcat 5 with 600meg of space and 10gig of data transfer. But Daily Razor's RazorBLAZE package attracts me because they also supporting Cocoon cost 19.95 american dollars a month for 5gig of space and 80gig of data transfer which is fantastic in comparision. VPS land seems ok too at 3gig of space and 40gig of bandwidth. One of the things I loved about Interadvantage which seems hard to to come by is, the friendly and knowledgable system administrator. The System admin has been working with me for quite some time and I know for a fact that this email was something he didn't want to write. We tried to get Cocoon working in a shared environment but came to the conclusion that it was not possible with serious security overrides. So please don't blame the ISP for this letter, its my fault for trying to slot a popular blog and amazing blog software in a shared environment. I'm sorry to the other people on the same server and I'll be moving soon.

So if you have any other hosts which do Java servlets, allow for at last 5gig of transfer data a month and cost as little as 10 pounds a month do please recommend them to me in the comments.

Comments [Comments]
Trackbacks [0]