Both i18n_node and translation_overview overwrites the node translate path:
node/%node/translate

Thus the two modules conflict.

I expect that most multilingual installations build on i18n (containing i18n_node).
drupal.org/project/i18n

We should find a better way to extend the translate tab.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

miro_dietiker’s picture

mvc’s picture

note: this bug also causes problems for entity_translation: #1174242: Properly override the node/%node/translate menu router path

stefan.r’s picture

Title: Conflict with i18n_node » No way to assign existing nodes as translations with i18n_node
Issue summary: View changes
Related issues: +#1632340: No way to assign existing nodes as translations with i18n_node
stefan.r’s picture

Priority: Normal » Major
Status: Active » Needs review
FileSize
1.93 KB

Workaround attached

portulaca’s picture

+1

james.williams’s picture

The attached patch resolves an issue (which caused a notice) around whether the tnid already existed or not.

stefan.r’s picture

Status: Needs review » Reviewed & tested by the community

Looks great, thanks

stefan.r’s picture

Status: Reviewed & tested by the community » Fixed

Committed and will be included in 2.0-beta2, thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.