Scenario:
Site formerly on node-based translation and then upgraded to entity field-based translation.
entity_translation_upgrade module un-publishes the suplemental nodes, essentially one node to handle both translation instances.

Unfortunately node-based function i18n_node_i18n_translate_path still overrides functionality because it still detects
unpublished supplemental translation node. Solution: add fail-safe if supplemental translation node is un-published do not use its obsolete information.

Solution
translation_node_get_translations($tnid) should add an additional filter Status = 1 (published)

Comments

chriscalip’s picture

chriscalip CreditAttribution: chriscalip commented

More context:

entity translation upgrade when switching from node-based translation to field based translation; process only disables (status) supplemental translation nodes.

chriscalip’s picture

chriscalip CreditAttribution: chriscalip commented
Title: Translation module , function translation_node_get_translations should accomodate node-based trnsltn & entity field-based trnslt » function translation_node_get_translations should accomodate node-based translation & entity field-based translation
drzraf’s picture

drzraf CreditAttribution: drzraf commented

Do you mean that unpublished node-translations should not be taken into account by entity_translation_upgrade when switching a field to field-based translation ?
Would this be related to the fact that it seems impossible to switch several fields to field-based translation as the entity_translation_upgrade batch only works once ?
Isn't this bug report related to the "Entity Translation" project ?