Here is a very simple patch for importing nodes with UUIDs (http://www.drupal.org/project/uuid).

New nodes will be created (new NID, same UUID), existing nodes will be updated (same UUID, existing NID on target site).

The NID does not have to be the same on both sites because it will be using the UUID that was generated for the node when it was created.

This does require UUID being used initially so each instance of a particular node shares the same UUID.

It's been useful for me...pretty quiet on the UUID front, but hopefully someone else finds it useful as well.

Sponsored by DLC Solutions, LLC. (http://www.dlc-solutions.com)

CommentFileSizeAuthor
node_export_uuid.patch545 bytesdjdevin

Comments

danielb’s picture

danielb commented

It sounds like a good idea, but I haven't looked into it much. It would have been a lot better if this was a more popular concept.
The idea we had to allow an admin to pick the fields/properties of a node on which to base these decisions on would still work well if there was a uuid or equivalent field in the nodes.

danielb’s picture

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

danielb commented
Status: Active » Fixed

I'm not going to use the patch, however I am going to use UUID integration to address these issues:

#753544: Features Support
#709558: Handle existing node skip
#744758: Handle overwriting, skipping, and nid preservation
#985848: Handle references

I've made UUID module mandatory for future installations of Node export for Drupal 6.

I don't know if I'll leave it that way in the long run, but for now it seems a safe bet.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.