Translation nodes are lost if interface language == language translated to

I will set up a test server with minimal install and see what happens, it does happen with blog nodes on my blog online.

I encountered the same problem once more, but now that I have a better insight into how the translations are stored I can at least tell you what happen. I have a node, I'll call it "English" which I go to the translate tab to create a translation. In the tab I select to translate into "Norwegian". When "Norwegian is stored in the database it has a nid and it also has a tnid, which refers correctly to the "English" node's nid.

But in the translation local task, which is where I am returned after submitting a translation, you will see only the "Norwegian" node. A quick check of the database shows that the "English" node has not had its tnid set to anything.

I have tested this on a clean drupal install, without any i18n, and then I have had no problems. It might be related to i18n_synch, which is a module I rely on heavily.

The quick workaround is to just update the database with the right tnid for the original node.

Unfortunately it doesn't happen every time, and there doesn't seem to be any rhyme or reason to when it happens.

In 6.x-1.0 I had the change interface language to translation language active when I relived this problem.

This is a duplicate of http://drupal.org/node/364319 I believe...

Please mark as duplicate if the 5.x issue I linked to in my previous comment automatically will be fixed for 6.x. I set this to active again, just in case it might be an issue to port forward.