No way to assign existing nodes as translations with i18n_node [#1632340]

In i18n_node you can assign existing nodes to be translations of the current node (the second table on node/%/translate). With translation_overview enabled there does not seem to be a way to do this.

Please also display the "assign existing node as translation"-form from i18n_node if it is enabled.

Comments

Comment #1

bnayal commented 14 March 2013 at 12:38

Hi,
I need this feature also, any change on it?

Thanks

Comment #2

guillaumeduveau

Toulouse

commented 22 January 2014 at 08:11

Title:	No way to assign existing nodes as translations …	» No way to assign existing nodes as translations with i18n_node
Version:	7.x-2.0-beta1	» 7.x-2.x-dev
Category:	Bug report	» Feature request
Issue summary:	View changes

This is annoying because it means the module is not quite usable with i18n_node, since it takes over the node translation tab, which i18n_node also tries to take over.

Comment #3

rad_one commented 31 January 2014 at 11:18

Hello all,

I use Translation Overview 7.x-2.x-dev. And when I enable it, "Select translations form" is not showing.

here when TO is disabled: https://drive.google.com/file/d/0B4pRnRRvx7epdXJNMC1ONVNnQkE

here when TO is enabled: https://drive.google.com/file/d/0B4pRnRRvx7epZDA4YzVleDVoVmc

Thanks for any help.

Comment #4

anybody

German

Porta Westfalica

commented 10 July 2014 at 11:15

Priority:

Normal

» Critical

I can confirm the problem. It seems that this module hooks in and throws i18n_node out completely. This is CRITICAL for site administrators and important i18n functions! Setting up priority!