#68040Inline localize and/or synchronize does not respect sorting
Description
Working with IRRE in multilingual projects you often have the situation, that elements have been translated already but they need to get additional content, which has been added to the default language records.
For this purpose there are two buttons in the editing form of the IRRE parent to either “localize” and/or “synchronize” the elements. While the first will just add new elements, the latter will even remove elements that have been deleted in the original language.
These actions are working quite well with a small exception: The sorting of the default language children is not respected, since new translated elements are just added after existing elements, even when they actually have been added between existing elements in the original language.
This leads to completely broken structures especially with deeper nesting levels of extensions like i.e. Gridelements. We noticed that while preparing the Localization Manager for Gridelements support and first thought it was a bug in either l10nmgr or GE. But while testing the manual localize/synchronize functionality, we found the same buggy behaviour.
IMHO the sorting must be synchronized from the default language after adding/removing elements in the target language.
Reviews 2
Related issues 6
- Bug #43158Sorting of parent records also moves inline childs
- Bug #50310DataHandler fails to correctly re-sort (content) elements after moving one to top
- Bug #75400Related child elements don't get correct sys_language_uid during localization of parent record
- Bug #83079wrong sorting of content elements when translating using non-default-language CEs as source
- Bug #83469Translation of translations break sorting in tt_content
- Bug #84228Output error reasons if Build/Scripts/checkIntegrityCsvFixtures.php fails