Hi,

I got an issue using node_export_features, when reverting features :
When a node with the same uuid already exists, instead of replacing the node, it creates new node and try to recreate existing uuid (with duplicate keys failure).

CommentFileSizeAuthor
#1 node_export-replace_node_with_same_uuid-1470964-2.patch542 bytesbear_beavis

Comments

bear_beavis’s picture

bear_beavis commented
StatusFileSize
new node_export-replace_node_with_same_uuid-1470964-2.patch542 bytes

Here is a patch which use hook_nodeapi, so reimport will replace nodes with an existing uuid.

danielb’s picture

danielb commented
Version: 6.x-3.2 » 6.x-3.x-dev
Component: Features integration » Node export
Category: bug » task

This isn't really a bug, nor is it something that should be addressed in the node_export_features module, nor is replacing the old node the intended default behaviour - we have never discussed this or decided to do that.

UUID integration was added so that one day we would be able to create such a feature, but that feature hasn't been created yet.

Development regarding this has stalled since the UUID project was very stagnant last time we looked.

danielb’s picture

danielb commented
Status: Active » Closed (duplicate)

The question of what we will do about these sorts of issues will be addressed in #744758: Handle overwriting, skipping, and nid preservation