Thread Starter
zota
(@zota)
Ah ha. The plugin isn’t broken per se. It just looks like the 3.1 export format has changed, and it is now incompatible with the current plugin.
I’m guessing that wordpress.com uses the same export format as WordPress 3.1? I followed the instructions for editing a wordpress.com WXR file to fix the category/tag incompatibility at this post:
http://wordpress.org/support/topic/lost-categories-in-import-of-wordpresscom?replies=12
It worked. Tags are imported as categories, but I can deal with that by importing one category at a time.
If WordPress.com is using the 3.1 format then you’ll want to use the development version of the importer.
Found here and direct download link here.
This is a pretty big issue so will see what can be done about pushing a release here.
Thread Starter
zota
(@zota)
Oh hey, development version. I’ll give it a shot.
This will be a really big issue when 3.1 officially rolls out. Exports incompatible with imports, dogs and cats living together… mass hysteria!
This will be a really big issue when 3.1 officially rolls out. Exports incompatible with imports, dogs and cats living together… mass hysteria!
That definitely will not happen. I was talking about getting a release ASAP instead of the planned time which is with or just before 3.1.
Let me know if you have any problems with the development version 🙂
At aventar.eu we started moving from self hosted to wordpress.com and we had the same problem. We are running wordpress 3.1. So, at our self hosted installation, I replaced the files wp-admin/includes/export.php and wp-admin/export.php with the ones from version 3.0 and the wordpress.com import was successful. All tags and categories are correctly assigned.
So, this is a workaround while wordpress.com doesn’t have an import compatible with wordpress 3.1.
Note: if you want to try this, don’t forget to backup your original 3.1 version files of wp-admin/includes/export.php and wp-admin/export.php
To download old releases: http://wordpress.org/download/release-archive
