Hi! I'm running this on Drupal 6.17. When I do the import, I get a success message, complete with how many posts got imported, etc.

But there is no content. It's like nothing happened.

Prowling around the database, I do find my data, though. Everything seems to be locked in a single, huge row in {ctools_object_cache}.

How can I try to debug this? Since wordpress_import is giving me a success message, I'm not sure where to look for errors. :)

Thanks very much!
bakersman

Comments

lavamind’s picture

lavamind commented
Assigned: Unassigned » lavamind
Status: Active » Postponed (maintainer needs more info)

Are you using PHP 5.3 by any chance?

Please try the import using the 6.x-2.x-dev version and see how that goes.

wwwoliondorcom’s picture

wwwoliondorcom commented

Hi,

I have the same problem withthe Drupal 5 version, what can I do ? Why doesn't the content show up ?

Thanks.

lavamind’s picture

lavamind commented

@wwwoliondorcom: The Drupal 5 version of this module is completely different, and is no longer supported, sorry.

Anonymous’s picture

Anonymous (not verified) commented

Sorry for the long delay! I thought I was configured to get an email on new comments.

I checked -- I was using PHP 5.2.13 :)

But, you can close this issue. I used another module. :) This one looks really good, but it probably just needs a more recent PHP version than I could easily get to work.

Thanks!

danny englander’s picture

danny englander
(he/him)
commented

I am having this same issue, not sure if this was ever resolved. I am using PHP 5.2.13. Should I open a new issue or use this one? To reiterate, I completed the import, got a success message and it showed what was imported but then I don't see any content either in Drupal's listing of nodes or in the DB.

Drupal 6.19
Wordpress Import 6.x-2.x-dev (2010-Nov-12)
PHP 5.2.13
MYSQL 5.0.91

lavamind’s picture

lavamind commented

@highrockmedia, and others having this problem.

Unfortunately I can't reproduce the error you describe. It would help a lot if you could upload the WXR file that is producing the problem.

antoniotorres’s picture

antoniotorres commented

I'm using PHP 5.3 and I'm getting the same problem, is there anything special or problematic about it? I saw you asked about it.

antoniotorres’s picture

antoniotorres commented

I used the .dev version and it worked. WOOT! So awesome.

ron_sparks’s picture

ron_sparks commented

what version of Drupal are you using, I am having the same issue, I tried the dev version of Node Import on Druple 6.16 and no dice, I have sense upgraded to 6.20 and wondering what you are using and if this would make a difference or not...

egulias’s picture

egulias commented

Using Drupal 6 with PHP 5.3, with the .dev module this issue was solved. Comments here where really usefull, thanks.

lavamind’s picture

lavamind commented
Status: Postponed (maintainer needs more info) » Fixed

This is fixed in latest stable : 6.x-2.2

Anonymous’s picture

Anonymous (not verified) commented

Indeed, 6.x-2.2 works great. Thanks for the note.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

brightbold’s picture

brightbold
she/her
Primary language English
Location Boston, MA
commented

I was experiencing what seemed to be this same problem, but I was using 6.x-2.2, where it was reported fixed. Eventually I realized the content was in fact in the database, just not showing up in lists of content. However if I browsed to the node and edited it, then it would appear in the list.

The problem appears to have been caused by some required fields in my content type that were not being filled in for the imported WordPress posts. Two of the fields were taxonomy fields, and the other two were from Domain Access - "publish to" and "source domain." I ended up resolving the problem by deciding I didn't need the Taxonomy and creating a new content type for the imported nodes. This still has the Domain access fields but for some reason seems to be filling in Source Domain by default; the other field still isn't filled in but after re-importing using the new content type, all the imported nodes are showing up in the Content list. (Temporarily removing the "required" setting from the fields on the content type might also have solved the problem, then I could have used VBO to fill in the required fields and changed it back to required.)

I didn't test enough to determine exactly what caused the problem, but if you're experiencing this same issue and you're using 6.x-2.2 or higher, hopefully this will help you in troubleshooting.