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.

CommentFileSizeAuthor
#6 translation_overview-assign_existing_nodes-1172530-6.patch2.02 KBjames.williams
#4 1172530-3.patch1.93 KBstefan.r

Comments

miro_dietiker’s picture

miro_dietiker
Location Switzerland
commented

This is a followup for
#1158294: Patch that resolves all the issues with 7.x

mvc’s picture

mvc
they
Primary language English
Location Montréal, CA
commented

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

stefan.r’s picture

stefan.r commented
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

See also #1632340: No way to assign existing nodes as translations with i18n_node

stefan.r’s picture

stefan.r commented
Priority: Normal » Major
Status: Active » Needs review
StatusFileSize
new 1172530-3.patch1.93 KB

Workaround attached

portulaca’s picture

portulaca
she/her
commented

+1

james.williams’s picture

james.williams
Location Coventry, UK
commented
StatusFileSize
new translation_overview-assign_existing_nodes-1172530-6.patch2.02 KB

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

stefan.r’s picture

stefan.r commented
Status: Needs review » Reviewed & tested by the community

Looks great, thanks

stefan.r’s picture

stefan.r commented
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.