#21161Problem with moved translated content elements (wrong column)
Description
There is a problem if you´ve got an website with 2 or more columns and more than one language. If you shift a content element (the default lang) from one column to an other, only the default language gets the new column attribute, the translated elements holds the old column. In the frontend it doesn´t matters because only the column attribute from the default language counts (that means in FE it looks good even though in BE it is wrong).
(issue imported from #M15413)
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 5
- Task #66540Avoid having content jump up and down when dragging elements
- Bug #72547Moving orig tt_content records does not move translated records
- Bug #81753Content element translations dissapear in page module after move to another column
- Bug #95069Add eventDict to DragDrop JS lib
- Epic #101557Translation Handling Findings