I tried to use the field collection with the node_clone. It aparently worked but when I edited a field that was part of the field collection, it edited on the original and on the new node. It seems that the Node Clone is cloning the reference for the field collection and not creating a new one. Is it possible to fix that? When the user clones a node with a field collection would be better to have it also cloned.

Comments

eott’s picture

eott commented

Been working on this myself, but haven't started testing the solutions yet. There are open threads on the same issue in both node_clone and field_collection module. Check out http://drupal.org/node/1304214 and http://drupal.org/node/1233256. You could try the field_collection patch in comment 28 of http://drupal.org/node/1304214; it is possible that updating to the most recent dev version of field_collection might help, too. HTH!

RumpledElf’s picture

RumpledElf commented

I know this doesn't help, but just hit this issue myself - mine it caused a flurry of "oh heck" when I deleted some content from one cloned node and it was gone from all of them, and had to get it back.

Hopefully this gets fixed eventually, certainly can be a nasty interaction between the two modules if you aren't expecting it.

itangalo’s picture

itangalo commented
Status: Active » Closed (duplicate)

There's an issue about this here: #1233256: Integrate node_clone with field_collection module

It also links to this issue, where I found a patch that solved the problem for me: #1304214: Doesn't clone properly

(The patch is against Field collection, not Node clone.)