I just tested the dev version of node import. The import looked like it was successful (0 rows with errors) but no nodes were actually created (or at least that I can see) when I visit admin/content/node. Is there another step to actually create the nodes or was this disabled for testing?
Comments
Comment #1
Robrecht Jacques commentedNo, there is no other step and it was not disabled in the -dev branch.
Did you use the -dev version of 14 feb or the one of 23 feb?
Could you attach the "Node import debug report"?
Comment #2
zirafa commentedI think I figured it out. I had a custom module that was form altering the value of op = 'Save' of that particular content type. So what I think happened was on the last step, when drupal_execute was triggered it assumed that the submit button had op='save' but since mine had been form altered it didn't actually create the nodes.
When I turned off my custom module, the nodes were created.
I don't know if there is a way to fix this - perhaps node_import should explicitly set $form_state['values']['op'] to match the submit op for the particular content type, either by checking what it is or forcing it to be 'save'. This would ensure that when drupal_execute is run it will actually create the node.
Comment #3
zirafa commentedThe other thing I noticed was that all the nodes automatically were set as unmoderated. Perhaps there could be a setting to set the moderation bit for created nodes?
Comment #4
Robrecht Jacques commentedWhat module sets the moderation bit?
Good point about the Save button being renamed. I'll leave this issue open and changed the title.
Comment #5
zirafa commentedIt is the http://www.drupal.org/project/modr8 module that sets the moderation bit.
Comment #6
Robrecht Jacques commentedThe modr8 module has been added as supported in -dev.
Comment #7
Robrecht Jacques commentedDuplicate of #1130860: Conflict with Node Form Settings module.