#83079wrong sorting of content elements when translating using non-default-language CEs as source
Description
Steps to reproduce:
- make sure you have at least two “Website language” records (sys_language) in your root node. Let’s name them “A” and “B”.
- open the page modul
- create a blank page
- create at least three distinct content elements in the default language. Lets name them “1”, “2”, “3”, “4”
- choose the “Language” view in the “actionMenu” dropdown
- create a page translation for language “A”
- translate the content into “A” using the “translate” mode (not ‘copy’) * these content elements will be created in the correct order
- create a page translation for language “B”
- translate the content into “B” using the “translate” mode (not ‘copy’)
- choose “A” as translation source for your translation when the dialog asks “Choose the language from which you want to localize the content”
- the order for “B” will result in “1”, “4”, “3”, “2”
What happens:
The “localize” method in \TYPO3\CMS\Core\DataHandling\DataHandler calls “getPreviousLocalizedRecordUid” to determine after which CE the new translated CE should be placed.
This works okay for the first case (using default as source), but returns a wrong value, when using another translation as source.
Reviews 4
Related issues 9
- Bug #30469Sorting of localized tt_content elements is wrong after copying
- Bug #68040Inline localize and/or synchronize does not respect sorting
- Bug #78220Translate mode copy does not respect order
- Bug #81328Translation didn't sort Elements correct.
- Bug #83469Translation of translations break sorting in tt_content
- Bug #84951Localization: Copying new record in existing localization has off-by-one issue
- Bug #86059Wrong sorting for localized entries in page module with 8.7.16 and higher
- Bug #93968false order of localized CE in BE view / "Translate" button is shown but no translateable CE are available
- Task #96035More deterministic functional test DataSet