Bug #84951
closed
Localization: Copying new record in existing localization has off-by-one issue
100%
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.
Updated by
Updated by Gerrit Code Review almost 6 years ago
- Status changed from New to Under Review
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/56894
Updated by Gerrit Code Review almost 6 years ago
Patch set 1 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/56904
Updated by Andreas Fernandez almost 6 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 3c6cdaedd288a3514d48e99fe298870606769201.
Updated by
Updated by Christian Kuhn over 2 years ago
- Related to Bug #83079: wrong sorting of content elements when translating using non-default-language CEs as source added
Updated by Christian Kuhn about 2 years ago
- Related to Bug #81328: Translation didn't sort Elements correct. added
Updated by Christian Kuhn about 2 years ago
- Related to Bug #78220: Translate mode copy does not respect order added
Updated by Christian Kuhn about 2 years ago
- Related to Bug #93968: false order of localized CE in BE view / "Translate" button is shown but no translateable CE are available added
Updated by Christian Kuhn about 2 years ago
- Related to Bug #86059: Wrong sorting for localized entries in page module with 8.7.16 and higher added