Thanks, please let me know. I'm unable to test anything relating to the Mac. I'll update the page relating to the fact that Wordpress 2.3 is a problem re - converting.

I have a WordPress 2.5 site which I'm trying to import in to a Drupal 5.7 site. Both are on my OSX 10.4 system running as "localhost". When I run your import application it reports that it's able to connect to both databases for each of the sites. Once I attempt to do the import the following error is reported:

dbTarget.Error - BuildTermData() function.

... six times then

dbTargetError: Function ProcessCategoryHierachy
Message is: Duplicate entry '111-0' for key 1

dbTargetError: Function ProcessCategoryHierachy
Message is: Duplicate entry '127-117' for key 1

dbTargetError: Function ProcessCategoryHierachy
Message is: Duplicate entry '156-0' for key 1

dbTargetError: Function ProcessCategoryHierachy
Message is: Duplicate entry '182-0' for key 1

dbTargetError: Function ProcessCategoryHierachy
Message is: Duplicate entry '216-0' for key 1

and then proceeds to report that the import is done:

Categories: 113
Users: 2
Pages: 1
Posts: 365

NOTE: The numbers reported are wrong, it should be:

91 posts, 60 pages, 50 drafts, contained within 23 categories and 90 tags.

Okay, any chance you can upload your Wordpress 2.5 back-up sql file. There's obviously something contained within the category system that the converter is not correctly accounting for.

I should be able to figure it out as I'm familiar with the error when last debugging but I could only debug against a smaller dataset.

For what it's worth, it's also given me heart in that at least the Mac version is working.

I have the WordPress2.5 db backup file ready, where can I upload the file or perhaps suggets an email address.

I sent you an email, via your contact form, with details.

db backup file sent via email. Please let me know if it works for you.

I've fixed the problem and the new version can be downloaded from here.

With the new version, 1.02, any chance you could attempt to convert your Wordpress 2.3 file. I've got a feeling the problem relating to 2.3 was in fact the same problem that I've just addressed and fixed.

Sure, no problem... so WP2.3 to D5.7?

Yes, if you can, no hurry though.

I ran an import of WordPress 2.51

91 posts, 60 pages, 50 drafts, contained within 23 categories and 90 tags.

to Drupal 5.7 which produced:

113 categories, 2 users, 1 page, 365 posts.

is your application dealing with categories vs tags and does it also deal with posts that have not been published aka drafts?

They are the same figures I got when testing your database.

The page number merely indicates how many times records were retrieved from the database in one hit. That is, if you left the default settings in place, the converter retrieves 200 records (posts) at one time. If there are more than 200 posts then the converter retrieves another 200 records (posts) and so on until all records (posts) are retrieved. The page number merely indicates how many times the converter went back to the database to retrieve records and has nothing to do with 'page' or 'post' entries.

Tags and Categories are the same thing. Wordpress separates them from a user's point of view. In Drupal, all your tags were imported into a separate vocabulary which you can rename to 'Tags' if you wish. Further, for that particular vocabulary, you'll be able to further edit the settings to make it a free-form tagging system (type the tags as you create/edit posts) the same way you were able to do with Wordpress.

The other categories are imported into another vocabulary, which you can further edit as per above.

Yes, your drafts were imported as well. If you check your Admin / Content Management / Content you will see that all your drafts are tagged or marked as unpublished.

Thanks for the explanation... you might want to change how the application reports the results as it's misleading.

Currently ALL transferred content was created as a blog entry thus there are NO page entries.

Confirmed that category and tag entries transferred as you described and published vs unpublished also appears to be correct.

Yes, I agree with the misleading bit and will have to think of a new term for that activity (retrieving records from the db).

At the importing screen you could have selected 'page' as opposed to 'blog' and all posts would have been imported as 'page' entries or 'story' entries if story selected.

Unfortunately with 50 pages and 200+ blog entries it's really not ideal to choose one or the other. Is it difficult for the transfer to respect the WordPress content type?

For what it's worth, I'm also seeing errors at the top of the page when I post me responce:

Don't you just love me, an endless supply of bugs :)

Those annoying comment error messages are p..... me off as well. I've raised this issue over at drupal.org. Everytime I think I've fixed it, days later, it's back. It's a Drupal 6.x thing.

Regards associating Wordpress posts/pages to Drupal's story/blog/page, that is doable. Within Wordpress all your 'post-types' were either post, page or attachment. I'll have a look at incorporating that for the version after next (maybe the very next version).

Hey, I don't mind being told of problems whether it's the converter or this site. At least I can then address things.

For what it's worth, I'm also seeing errors at the top of the page when I post me responce:

* warning: strtr() [function.strtr]: The second argument is
not an array in home/yhostcom/ public_html /cms/drupal-6.2/

As you can tell, I've reverted back to the stock-standard Drupal forum. This particular bug appears to be related to the 'Advanced Forum' as the errors don't appear now.

update: spoke too soon, yes they do. Might as well revert back to Advanced Forum - at least it looks better (in my opinion).

Well I hope the title of this comment doesn't make a liar of me.

On my test site I've updated to the latest 'Token' module and no errors are reported after posting comments.

Here's goes, about to 'save'.

Back to the drawing board. This is really p...... me off and I don't really understand why others over at Drupal.org are not ranting and raving about it.

Maybe it would help if I actually activated the 'Token' module.

Update: same problem.....

Sooo... back to the oginal topic of this thread?!? Any progress on the WordPress2.5 to Drupal6 application?

Two versions (I think) have been released since we last chatted. Version 1.03 which accounts for Drupal 6.x. Just the other day I released Version 1.04. For details of what's new in 1.04 click here.

I've also updated the manual and you'll note that each of the Wordpress page types and status can be specifically associated to a Drupal content type. Screen shots here.

Sweet, thanks!

I've solved the problem of error messages appearing after each comment is posted. Well, haven't really solved it, just hidden the error display - so that it doesn't write to the page.

This is administered from Administer / Site Configuration / Error Reporting. Simply select the option to only report to the log, rather than the log and the screen.

It's a problem that still needs to be fixed.