I ran into a major problem with the Node Export module... on my remote site I use drush to export all nodes of a certain type into a text file. Then I move that file to my local site and import the file, also using drush. The problem is that new nodes are created during the import, so that existing nodes gets duplicated. And yes I have checked the option "Create a new revision of the existing node" (if the node exists).

A very strange thing is that if I export the nodes locally and then re-import them again locally, this does not happen. But my remote site is identical with the local one, and the nodes do have the same node IDs. I have checked and double checked that.

Please help me understand why the export file from the remote site is treated differently during import, so that nodes get duplicated?

Or do I need to find another solution for this remote export->local import?

Comments

Tommy_001 created an issue.

Tommy_001’s picture

Tommy_001 CreditAttribution: Tommy_001 commented

I looked at the UUID on the remote site and the local site and these were somehow not identical, which I think is a bit strange. But anyway, I clicked the Create missing UUIDs on the config page locally, made a new backup of the database, loaded that backup on the remote site, exported nodes from the remote site and then imported them back on my local site. And this time it worked. Beforehand I also checked that the UUIDs on some random nodes were identical on the remote site and the local site.

So now it seems to be working after all. I will add this extra step of double checking that the UUIDS actually are identical on existing local and remote nodes, before the next export-import procedure.