Project

General

Profile

Actions
Copy link

Bug #84951

closed

Localization: Copying new record in existing localization has off-by-one issue

Added by Andreas Kienast almost 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
DataHandler aka TCEmain
Target version:
Candidate for patchlevel
Start date:
2018-05-09
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

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.

Related issues 5 (1 open — 4 closed)

Related to TYPO3 Core - Bug #83079: wrong sorting of content elements when translating using non-default-language CEs as sourceClosed2017-11-24

Actions
Related to TYPO3 Core - Bug #81328: Translation didn't sort Elements correct. Needs Feedback2017-05-24

Actions
Related to TYPO3 Core - Bug #78220: Translate mode copy does not respect orderClosed2016-10-10

Actions
Related to TYPO3 Core - Bug #93968: false order of localized CE in BE view / "Translate" button is shown but no translateable CE are availableClosed2021-04-22

Actions
Related to TYPO3 Core - Bug #86059: Wrong sorting for localized entries in page module with 8.7.16 and higherClosed2018-08-31

Actions
Actions
Copy link

Also available in: Atom PDF