Project

General

Profile

Actions

Bug #92783

closed

Record inserted on wrong pid

Added by Philipp Parzer over 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Start date:
2020-11-06
Due date:
% Done:

100%

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

Description

If a record is localized and then moved to another page(A), the l10n_source field of the translated record on the old page(B) points to a record on a different pid(A).

If you create a new content element after the moved item on the new page(A) and want to translate it, the translated record of the new element is inserted on the old pid(B) because TYPO3 selects the record before itself by order and then selects the localized record by l10n_source which is on the old page(B).

This can lead to strange situations if records are copied and/or moved to different pages.

In this commit, the behaviour to use the l10n_source rather than the l18n_parent was introduced:
https://github.com/TYPO3/TYPO3.CMS/commit/3c6cdaedd288a3514d48e99fe298870606769201


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #92198: Localize method gets wrong PID from records generated during former free mode translationsClosed2020-09-04

Actions
Related to TYPO3 Core - Bug #93078: 9.5/10.4: DataHandler::getPreviousLocalizedRecordUid() does not check pidClosed2020-12-15

Actions
Actions

Also available in: Atom PDF