Translating nodes duplicates content, not linked

Yes, I'm experiences the same. The nodes are not linked together.

UPDATE: I disabled the Synchronize translations module, and then everything works as expected. It looks like some of the fields I have specified have problems with synchronizing, and the linking is therefore not completed. I will investigate some more.

Has there been and progress with this?

We need to know about which fiels cause this with i18n_sync.

Closing, no follow up. Please reopen when you can post the missing information (which fields).

i can confirm it. i am testing now what fields cause that and report back. it seems it happens if you chose body . i created a node and translated it. source EN, to DE. then i turned on sync body. returned to the node and switched from EN to DE (language switcher) then connection is lost between the two.

Notes:

1.) Enable translation for Basic Page, save
2.) Create a node of this type in EN (EN is default language)
3.) Hit translate tab and click "add translation" (this case german), save node.

Checking the node object of the translated node(DE): http://www.root.artwaves.de/screensnapr/1338400760-jr6EFk.jpg
now at the url of the translated node de/page/deeee the language switcher block shows to languages EN/DE, hit EN. Language switcher now only shows EN.

Checking node object: http://www.root.artwaves.de/screensnapr/1338401226-GeqfCD.jpg

Question

The source node should have tnid = nid? meaning pointing to itself (see above image, its not)
http://www.root.artwaves.de/screensnapr/1338401161-J4k6ha.jpg

Solution

Disable entity cache for nodes! #1360042: Make Entity Cache configurable?
Thanks to webflo

Related too: #1405234: Implement update hooks for node translation sets. Clean-up node translation sets.

As e-anima says, the source node should have its own nid as tnid. Once I figured out that this was the cause of the problem, the solution was actually quite simple and Entity Cache can still be enabled. I created a patch for this which seems to work well, read more about how I solved it at http://storleden.se/blogg/solution-fundamental-tnid-issue-i18n

Wow, it certainly is not easy to create a patch that passes automated testing!

I don't think there's been any more progress on this. The patch failed testing on:

• i18nSelectTestCase
• I18nNodeTestCase
• i18nVariableTestCase

Would be good to find someone to rebuild the patch with new test cases though.

In the meanwhile patch #8 solved this problem :-)

Re-test on dev branch.

#8: fixtnid-1463402-8.patch queued for re-testing.

Ok, so we need to adjust the i18n_node.test on line 50 & 62 so that I18nNodeTestCase->testAddContentToTranslationSet() returns the correct value.

This patch has been sitting there since June. Can someone please re-roll another one against the current dev version of the code?

I have some concerns about this patch...I think the solution should be in entity cache and not i18n. We encountered this issue recenty and in looking into it the tnid getting set on the translation group is being done by the core translation module. Going in with a hook and re-writing it after seems like a bit of a workaround for a more systemic problem that exists within entity cache which causes a problem with core translation.

Agree with #18
Since this is something between Content translation (core module) and Entity cache, moving to Entity cache module.

Marking this as a duplicate of the more established #1349566: Add tests for content translation.

I have the same problem and I don't have Entity Cache enabled.
Drupal 7.25

The problem exists even if entity cache isnt enabled.My version of Drupal is 7.25

@maggie_drupal I would suggest you keep this issue closed and re-open a new issue with more information s to your configuration and symptoms. I did quite a bit of debugging on this issue and this one in particular is definitely with entity_cache. That being said, at this stage in the game I would be using entity translation and not content translation which would circumvent this problem.

Closing the issue, I'll open a new one.

We have the same issue but no entity cache module enabled, so I am searching for your post @maggie_drupal, but it seems you never created a new ticket? If so please tell where it is :) Thanks

For those who don't use "entity cache" module and are having this issue:

Looks like I found the issue, please see this ticket here which solves the problem for me.
See comment 24 which has the patch (and seems to be in the current dev release of i18n).

• https://drupal.org/comment/8370891#comment-8370891

This, or my issue, also had nothing to do with the "entity cache" module. (not using it)