It doesn't work with WP 4.0

Today the imorter was updated and IT WORKS!

Thanks, Tom

I just installed the plugin ten minutes ago and it does NOT work with 4.0! I get No posts matched your criteria. showing on every post that it did “import” which is telling me there is no data. I think everything gets shifted on row from the wp_posts table as I believe there is an additional row for 3.8 (39 rows) and 4.0 has 30 rows of MySQL entries:

FULLTEXT KEYpost_related(post_name,post_content)

*…everything gets shifted ONE row….

my user agents:
WordPress Importer Version 0.6.1

Exported from WP v 3.8.4 Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.104 Safari/537.36

Impotered to 4.0 Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:33.0) Gecko/20100101 Firefox/33.0

tradesouthwest, do you have installed php-xml?
I had a blank page result about the import process, but I forgot install php-xml.
CentOS 6.5:

#yum install php-xml -y
#servicde httpd restart

Works for me.

Unfortunately it is not an installation of WP on my localhost, it is on a shared hosting website. My localhost is Debian 8… I have not tried it there but it turns out that I need an app much more versatile to change fields from one post type to another (wpbdp_post_fields to geodir_post_fields).

I am still not sure what ceeps this ‘new’ version of WP Importer from working on 4.0 rather than the old 3.8 has FULLTEXT KEYpost_related(post_name,post_content) and 4.0 does not.

My export from one site was from WP 4.0 and the import in the other was WP 4.0 too. And this did work okay.
It’s probably better to update to 4.0 first and than export the data.

Why would the plugin work on 3.8 and then it was upgraded to work on 4.0 but now it does not work on 3.8?

There are some plugins in the (export) site that do not work with 4.0 so we chose to not update. I might have to down grade the new site from 4.0 to 3.8 then import.

Ultimately I may end up using PHPMyAdmin.

Thanks m2f0! Had the same issue with WordPress importer showing a blank page on import, and it turned out I had not installed php-xml on my CentOS server.