PBahner
commented
3 weeks ago I have this problem too.
Problem
All content elements (original language as well as translated language) are displayed as children of the default language container:
In the translated container they are shown as untranslated:
Possible Cause
The problem is caused by incorrect referencing of the container in the child elements.
The b13 container extension will only work correctly if all child elements are referrencing to the default language container (with tx_container_parent in db). The translated nodes must not reference the translated container.
The t23_inline_container does the opposite. The translated childs reference to the translated container.
When I change the tx_container_parent of the translated childs to reference the translated container, the inline elements will be displayed correctly for each language but the translated child will be shown as unused at the bottom of the page:
h-e-l-l-o-w-o-r-l-d
Not sure if this is an issue with container or with the t23_inline_container but:
Current Situation:
When translating container contents without t23_inline_container, the tx_container_parent field stores the default language parent ID.
Translated content appears as children of the default language container in the tx_t23inlinecontainer_elements field.
The container translation shows tx_t23inlinecontainer_elements as untranslated.
When adding new elements to tx_t23inlinecontainer_elements in the default language and translating them, existing translations are updated to a new tx_container_parent, which is now the translated container ID. This fixes the backend view.
Regardless of tx_container_parent, the frontend correctly renders translations.