Changing colPos of content elements in "additional languages" fails when using Workspaces
In the "Live" workspace, and working with content elements in default language, changes to the colPos of a content element will be auto-inherited to the additional languages. This is the expected behaviour.
When working in other (draft) workspaces, the same change to the colPos of a CE will NOT be inherited to additional languages.
Manual changes to the colPos of content elements in additional languages are not possible / are not saved.
(Tested on TYPO3 8.7.24 with config.sys_language_overlay = hideNonTranslated )
Updated by Riccardo De Contardi almost 5 years ago
Either I am doing something wrong, or I can't figure how the change in colPos propagates from the default language to a different language :/
- I am using a clean TYPO3 8.7.24 installation
- I have a default language (italian) and another language (english, UID=1)
- everything is done in LIVE workspace
1. I created a page and translated it
2. I created a content element in "normal" column (colPos=0)
3. I translated the content element ("connected mode")
3.1. the translated element has colPos=0, too
4. I edited the element in default language, changing the column to "left" (colPos=1)
- the translated element still has colPos=0
- editing the translated element, the colPos dropdown can be changed (unlike for example Publish Date and Expiration Date, that are inherited from the default language and are disabled in the alternative language)
Am I doing something wrong? What am I missing?
Updated by Riccardo De Contardi over 3 years ago
I repeated the test of my comment 1 with 9.5.20, 10.4.6 and latest master;
- the colPos value of. the translated content. still does not change with the change of the original one
- but the field colPos in the translated content is actually editable
Is this the correct behavior?
Updated by Jo Hasenau 5 months ago
This bug can still be reproduced at least in CMS 11.x but not just within a workspace - moving an element to another column via drag & drop will leave the connected translated element in the former column.
Sorting will be inherited though as long as it happens in the same column.
And with more then one element moved to another column sorting will be inherited too. Even though the translated elements stay in another column they will still be sorted.
Having Gridelements installed will "fix" that bug, since there are some DataHandler hooks in place that take care of any kind of column changes within and outside of Gridelements containers.