Hi,

I tested your module but I didn't see options to skip a node when an existing node already exist, so it add a duplicate.

It would be great to have an option like that. If a node of the same nid already exist, don't replace it. Or even better, provide some options to choose what are the criteria that make a node considered as existing or not (nid, field, other...)

It would be very usefull and will avoid the deletion of all nodes + import of all new nodes to avoid existing nodes issue.

Comments

danielb’s picture

danielb commented

It would have to be based on criteria, not the nid, since the nid of the same node on another site is almost always different.
Good idea. It might take a while to get this going, design the interfaces, and build it, but I like the idea.

danielb’s picture

danielb commented

Related discussion about overriding old nodes with a newer copy of the same node: #744758: Handle overwriting, skipping, and nid preservation
The idea of using criteria to determine whether a node is the same node could be used there too.

danielb’s picture

danielb commented
Title: Option to skip existing node » Handle existing node skip
Status: Active » Postponed
danielb’s picture

danielb commented
Component: Node Export » Node export
Status: Postponed » Active
danielb’s picture

danielb commented
Status: Active » Closed (duplicate)

Merging this issue with #744758: Handle overwriting, skipping, and nid preservation