Assign a cloned node as a translation of the original node

dup to http://drupal.org/node/1173362

Hi Kelley - were you successful in cloning nodes with existing translation ?
The module will clone the node, however the translated content does not get moved over in the clone.

Thanks for the update Kelley - I'm in the exact same predicament as you.
I read this :
http://drupal.org/node/365797#comment-3220040
but there is no explanation as to "why this is a good thing".

I've not used entity_translation but I'll go take a look right now.

The option my Comms guy would be satisfied with was if the textarea of the particular Content Type was pre-populated with "starter" content. So I'm looking at that as well as a work around.

Re #3: I have tested Node Clone with Entity Translation, and it does not seem to work properly: newly cloned node's language is undefined and non-editable, so you cannot do anything good with it until you fix this manually in the database.
Generally, I think it should work, and is quite promising - but something should be fixed in Node clone, to clone everything properly - the records in the 'entity_translation' table, all language versions of the fields (including the title_field that replaces the regular Title), and so on.

Agree!

GN, do you know if there is an existing Open Issue re: this fix for Node Clone ?

David, I'm only aware of this issue: #1342590: node_clone -> entity_clone, which seems to be kind of more global.

I think I ran into the same or a similar issue, except with entity translation. I'm not sure if this helps, but I thought I would mention it.

The problem:
- I configured the webform content type to 'enabled, with field translations'
- I created a webform (template) with English text
- In the DB, the node language was stored as "und".
- I cloned the node via the "Clone Content" link
- The "Translate" tab didn't appear for the cloned node
- In the DB, the cloned node language was "und".

I was able to fix this by going to Configuration > Regional and Language > Entity Translation, and under Node > Webform, setting the default language to English. After creating the template webform again, and then cloning it, the Translate tab appeared on the cloned node.

I don't believe this is a duplicate anymore, since the node referred to is about another issue (error notice), which isn't the case anymore. But the issue with i18n remains, be it on another level.

Basicly it should be possible to assign a cloned node as a translation of the original node. This is especially relevant when cloning a webform, since using the default translation method of i18n the form components are ignored.

I can't find a way how with the Replicate module, it seems like that Replicate module is even making it more complex (I have no coding background), in a way it would save more time to just translate a webform node the traditional way.

[Edit] For people in search of a quick fix:

1. Open your Drupal database
2. Open the table node
3. Find the original node
4. Find its column tnid and copy the number
5. Find the cloned (translated) node
6. Paste the copied number in its tnid column
7. Save and done

[Edit 2] Or you could just scroll down the translation overview after hitting the node's tab "Translate", and assign the corresponding node there. Seems like I wasn't paying attention :)