Bug #81753
Updated by Markus Goldbach almost 7 years ago
If the PageTS option @mod.web_layout.defLangBinding@ is activated and you move a content element to another column the translation dissapear in the page module.
In the list module the translation is still there and connected to the parent element.
In the frontend the translation is shown on the correct column.
*Exspected behavior:*
If I move a content element to another column the related translations were moved to the same column, too.
Reason is that the column of the translation isn't changed, so the translation is interpreted as standalone and won't be show, because the option @defLangBinding@ is activated and show only translation with parent elements.
*Steps to reproduce:*
* activated the PageTS option @mod.web_layout.defLangBinding@
* create a page and translate it
* create a content element and create a translate it by using the