In my efforts to get this working with data exported from node_export v6.x-2.x (or manually created) I uncovered two issues:
* The data is exported as a string in array format. In order to be part of a complete statement the eval() line needs to assign the nodes array within the eval() line.
* The function expects an array of node records, so nodes exported individually won't load.
Damien
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | node_export.new_export_format.patch | 1.81 KB | James Andres |
| #3 | install_profile_api-n402370-v4.patch | 870 bytes | damienmckenna |
| #2 | install_profile_api-james-node_export_v2.patch | 845 bytes | James Andres |
| #1 | install_profile_api-n402370-node_export_v2.patch | 1.28 KB | damienmckenna |
Comments
Comment #1
damienmckennaFix attached. This needs to be verified to still work with data exported from node_export v6.x-1.x.
Comment #2
James Andres commentedInstead of adding the
$multipleparameter, how about just counting/checking the$imported_nodesvariable to see if a wrapping array is necessary?I've attached a totally untested proof-of-concept patch.
Comment #3
damienmckennaHere's a patch to match the newly renamed contrib/node_export.inc in CVS. I've tested it and it correctly imported six nodes that were loaded through individual files.
Comment #4
James Andres commentedI have tweaked the patch a bit to better utilize the functions already existing in node_export project. Can you give this a test and see if it works for you?
I also made the node_export "save-edit" hook fire before saving the node, and I made a few cosmetic changes to reflect variables and terminology used in the node_export module.
Comment #5
James Andres commentedThis patch is working well for me, tested on another project I'm working on. Committed.