#84951Localization: Copying new record in existing localization has off-by-one issue
Description
The default language has two records, which are copied (not translated) into a different language.
A new record is added in the default language at any position. If the records gets copied into the other language, the calculated position is wrong, the record is one “slot” above.
The issue is caused by BackendUtility::getRecordLocalization() (called by DataHandler::getPreviousLocalizedRecordUid()) which uses the l18n_parent field to get the original record. For copied records, this is not correct, as the parent is always 0.
Reviews 4
- 11.5 72254[BUGFIX] Better sorting localizing records from non-default language
- main 54750[BUGFIX] Better sorting localizing records from non-default language
- TYPO3_8-7 56904[BUGFIX] Consider `translationSource` for fetching localized records
- main 56894[BUGFIX] Consider `translationSource` for fetching localized records
Related issues 5
- Bug #78220Translate mode copy does not respect order
- Bug #81328Translation didn't sort Elements correct.
- Bug #83079wrong sorting of content elements when translating using non-default-language CEs as source
- 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