There are now two programs that convert Wordpress blogs to Drupal.

The first relates to the conversion of Wordpress 2.1/2.2 and b2Evolution 1.9 to Drupal 5.x.

The latest accounts for the conversion of Wordpress 2.5 to Drupal 5.x and 6.x (as of version 1.03).

Select the appropriate manual.

I mentioned last week that the source code for the Wordpress to Drupal converter will be uploaded within the next day or two. Okay, I'm a bit out with my time-frame but I will be uploading soon, please be patient.

The converter is written using Realbasic. You will need access to the Professional version as that is required simply because MySql is involved.

To cut a long story short I've now got access to Realbasic and can compile the source code (there was an issue last year which prevented that from happening - and is why I took to C++).

So in the next few days I'm running my eye over the source code, re-familiarising myself with it before uploading it. I'm sure there will be lots of questions as to why things were done in a certain way so I'd like to be a little bit prepared.

Also I'll probably upload a later version (.exe file) which I never got around to fully compiling.

Download the converter program from here. The version is 5-07 and the filename will indicate which operating system.

For instructions on use refer to the manual.

Please note, I'll also upload the source code file for general download. That will be in a day or two.

The following was a comment from Ari - an Internet Marketing Geek offering a solution re - not being able to convert Wordpress 2.3 to Drupal. I thought this particular comment should be a post in its own right.

After spending a number of hours Googling for instructions as to how to downgrade from Wordpress 2.3 to 2.2 (in order to use the WordpressToDrupal tool), I discovered this quick and simple method:

First off, download Wordpress 2.2 from Wordpress.org, and install it in a seperate directory/database.

Then in your Wordpress 2.3 administration panel, click manage, then export. Download the export file to your computer.

Now in your Wordpress 2.2 administration panel, click manage, then import. Click Wordpress, and select the .XML file you exported from v2.3.

Congrats, you've just downgraded to 2.2, meaning you can use the Wordpress2Drupal tool!

Thanks Ari, very much appreciated.

New Wordpress Version 2.3

Apparently Wordpress 2.3 is out. Unfortunately the converter program, Version 5-07, will not convert this version. The main reason being is that some table names have changed. I've not looked any deeper than that for reasons to follow.

I'm unable to address this in the short term as things have conspired against me, preventing further development. One of those things is that I upgraded from Windows XP to Vista and in that process my version of Realbasic 2006r4, which is the program I use to develop the converter, contains a bug relating to MySql. The particular bug prevents program compilation, that is, converting it into an executable file. The RealBasic people tell me that that is fixed in the next version but that will cost me more dollars to upgrade.

Ruby Programming Language

I'm now looking into using another development environment to continue on with this pet project. The two main factors are that the development framework is free (or relatively cheap) or open source AND is available on all three major operating systems.

In my travels I've come across the Ruby Programming Language which is also the driving force behind the Ruby on Rails system (Web Development). These systems are 100% free, open source and cuts across all major operating systems.

Character Encodings

This version addresses the problem of weird characters ending up in the Drupal database and was as a result of incorrect character encodings. For what it's worth the Wordpress MySql database is encoded as 'Latin1' and the Drupal MySql database is encoded as 'utf8' (unicode).

I conducted some tests and specifically tested against this particular sentence:-

“Mares eat oats–and does eat oats—and…little lambs eat ‘ivy’.”

An encoding problem has reared its ugly head and giving me no end of grief.
At the Wordpress end, type in (or more commonly paste in) this line of text:-

“Mares eat oats–and does eat oats—and…little lambs eat ‘ivy’.”

I'll point out that the double quotes starting and ending the line of text are not double quotes, they are in fact curly quotes. Try and find them on your keyboard. Chucked in for good measure are a few other non-standard type characters.

This section details most of the problems regarding the converter. Why some things simply don't work. Actually, it won't be known initially why some things don't work but at least here I'm highlighting that I'm in fact addressing it, somehow.

Post Types

Previously, all posts transferred from Wordpress or b2evolution to Drupal were created as blog entries within Drupal. This might not be the preferred option of some users.

It is now possible to select either, Blog, Story or Page as post types that are created within Drupal.

To further clarify, any posts tagged as 'static' within Wordpress are transferred to Drupal and created as a 'Page' type post. This was the case in prior versions but thought I should mention it in the context of this paragraph.

Teasers

I've just uploaded a Mac version of my Wordpress / b2evolution to Drupal 5.x converter. It can be downloaded from here.

As per the Linux version, the Mac version is completely untested. At this point in time I have no idea whether it will work or not. I can't offer any advice on how to set it up on a Mac (or Linux) computer and so make the assumption that Mac users know what to do.

On compiling the Mac version I selected the option "Universal Binary" for the Mac. I believe this basically covers the different Mac versions. Other options available to me were compiling specifically to PowerPC, Intel etc. Before I go down that route I'd first like to know what the issues are with the current Mac version.

For Linux and Mac users, if the conversion is, just not happening, I'd be more than happy to convert for you. That would require forwarding to me an SQL backup file, I'd convert that file to Drupal and send back a Drupal SQL backup file. Hey, that's an alternative at least.