node import appears successful no error reports, but no new nodes

I'm facing the same problem too and have been debugging for hours.
I tried creating another node type exactly the same as the original node type, and did the import successfully with shock.

Same issue here. Imports all records successfully (apparently) but no new nodes are created.

Using the 6.x-1.x-dev version of the files I've finally got this working. Just one change is needed:
node_import.inc: 1973
from
$form = call_user_func_array('drupal_retrieve_form', $args);
to
$form = call_user_func_array('drupal_retrieve_form', &$args);

Man this is very frustrating. I have tried node import and of course everything looks great then you look for the content and nothing. Seems to be invisible.

Tried feeds and everything worked except for the Date Import. I would be fine with it but I am trying to import events so dates are a must.

Honestly I think Node Import is a much better module as the concept just makes more sense but if I can't get the content to show then its no good.

Someone please help !!!

@isterich

Thanks for the quick reply. Posted a question under the feeds link you gave.

I have the same issue.

Import runs successfully, no errors, but no nodes are created.

Regarding #4 that change resulted in "Call-time pass-by-reference has been deprecated" messages that prevented the import from even beginning. I thought maybe since they were only warnings that I could get past them, but when the first record attempted to import, the message was returned as the AJAX return value, which meant that the whole thing stopped dead.

If you're running PHP 5.3 check out http://drupal.org/node/763036 for a fix.

I have the same issue and I am running php 5.2 it looks like there is no fix right now from everything i have seen... it is frustrating.

I first had the WSOD on step number #4 fixed that and now I am here. I also have to import dates and from what I read above feeds does not handle dates, i'll have to look into it. day 4 of trying to figure this out. good luck all if i find anything ill post

idea would there be something with importing over id's that are already there then not overriding?

idk there is no error or feedback so theres no way to see whats breaking... :(

Same issue, though I am seeing jQuery errors in my logs http://drupal.org/node/1091506

Hi guys,

The crazy thing about this bug is that I ran an import with 4500 nodes and that was fine. I'd updated to the 1.0 release to fix date import issues.

However I just tried to run another import of 2400 nodes and this has "completed successfully" but alas there are no nodes.

Removing the ampersand on 1971 of node_import.inc will remove the PHP warning, but it is a warning so I believe this is a red herring as it won't halt the script, it must be something else that isn't returning an error?

thanks,

luke

Yeh! OK I've solved it for my issue, but I see there are a few duplicate versions of this problem in the issue queue and my solution might help solve some of those and ones on here.

Basically, I had a sudden moment of realisation after reading Q2U2's comment (http://drupal.org/node/894114#comment-3745490) about node import being very fussy about node form settings and that because I'd been using - http://drupal.org/project/nodeformsettings - I'd changed a few form attributes which might affect a standard node form submission.

Checking over what I'd set, I saw that the submit button value had been altered, now usually with a Drupal form if the post value of the "op" or submit button value doesn't match with what the form build value is then it fails (deemed security issue, like a mismatched token).

However I don't think this generates an error. To cut the story short, I reset the button from "Submit" back to the default "Save" and the import worked immediately...!

I think the node form settings module is just a custom hook_form_alter() looping through settings that the user has configured, so any hook_form_alters that are in place affect this too. So it might be worth checking any customisations that you may have made before trying node import.

It also explains why one of my imports for a different content type (which I'd not affected via hook_form_alter()) worked perfectly.

Anyway, hope that helps.

Thanks,

luke

The Node Form Settings module caused this problem for me.

If NodeFormSettings is causing this, the issue is a duplicate of #1130860: Conflict with Node Form Settings module.

If not, reopen it.

I'm upping this, because no nodes are still created for me under Drupal 6.19
Every steps are ok, no error, preview of new nodes ok, but at last step 8 : pouf ! Nothing !
I've checked all node import releases, patches etc, php 5.2.11 , 5.3 Nothing form nothing.
Pleeeeeeease Help

I ran into a similar problem importing into ubercart catalog. I had done a large run (which worked) and then decided the attributes were not right, so I deleted the nodes and file references from mysql to start over and the new import wouldn't work. I'd report being successful but nothing was imported.

Then I went and cleaned out uc_products and uc_attributes and the import started working again. If you have removed items and are trying to re-import make sure all the old references are out of the database.

Thanks Luke! I had been beating my head against the wall trying to figure out why an import that worked a couple days back wouldn't run today. I had changed the submit button value via nodeformsettings and reverting the settings fixed the problem straight away.

Try to use Firefox or Google Chrome while importing nodes for Ubercart :) It worked in my situation.

I have had this problem repeatedly -- running an import, and getting no errors but nothing created 'No New Nodes'.
Changing the line feed from Mac to Unix has changed the flow, but often replacing the 'No New Nodes' with a 'Failure to import n nodes' error. Is that progress? Still no informative error message.

I think the most consistent solution I have found (not too great but works enough to post it) is to trim the csv to a single record, and the fields to pehaps a guid/title. Then import this. This is usually successful, and I then can build out THAT PARTICULAR FILE to do a full import. You must re-choose this file each time.

This has to another benefit to this approach of making finding which data is tripping you up, since this is the common issue in importing csv files.

We had same issue here today (using Drupal 7). It turns out we saved the csv file with a MacBook and its format. Saving it for unix allowed us to import thousands of nodes.

So, check the file format!

I am having the same problem. I am not a developer and don't know how to apply patches. Is there any solution that anyone knows about for D7 (for someone who knows Drupal fairly well, but doesn't code, and hasn't ever written a new module or applied a patch.) Fairly desperate for any advice, thanks!

sorry, I posted this in the wrong place. I am having the same issue with the Feeds Module...will post it over ther.

thanks luke ! your solution is very well explained and worked great !

I switch to php 5.2.13 from 5.3.2 and it worked. Nice. I hear some people still had problems on 5.2. Just thought I should mention the quick fix. Will look at 5.3 work around.

If you're importing Ubercart products, make sure your SKU's don't have hyphens in them. That was my problem. Import went smoothly with no errors, but no products were imported until I made that change.