Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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.
Comment | File | Size | Author |
---|---|---|---|
#6 | translation_overview-assign_existing_nodes-1172530-6.patch | 2.02 KB | james.williams |
#4 | 1172530-3.patch | 1.93 KB | stefan.r |
Comments
Comment #1
miro_dietikerThis is a followup for
#1158294: Patch that resolves all the issues with 7.x
Comment #2
mvcnote: this bug also causes problems for entity_translation: #1174242: Properly override the node/%node/translate menu router path
Comment #3
stefan.r CreditAttribution: stefan.r commentedSee also #1632340: No way to assign existing nodes as translations with i18n_node
Comment #4
stefan.r CreditAttribution: stefan.r commentedWorkaround attached
Comment #5
portulaca+1
Comment #6
james.williams CreditAttribution: james.williams commentedThe attached patch resolves an issue (which caused a notice) around whether the tnid already existed or not.
Comment #7
stefan.r CreditAttribution: stefan.r commentedLooks great, thanks
Comment #8
stefan.r CreditAttribution: stefan.r commentedCommitted and will be included in 2.0-beta2, thanks!