Project

General

Profile

Actions

Bug #15339

closed

localization fails if content is moved from other language to default language

Added by Daniel Chabrol almost 19 years ago. Updated 5 months ago.

Status:
Closed
Priority:
Should have
Category:
Localization
Target version:
-
Start date:
2005-12-30
Due date:
% Done:

0%

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

Description

Hello!

I copied a page from an old site to a new one, to have some initial content. The old site uses german as default language (uid=0) and english as localization language (uid=1). The new one uses english as default language. So the copied english content shows up in the wrong language in the new system. So I moved the contests in the laguages view of the page module from right to left (into the default column).
But now the problem occurs: If you now press "copy default content elements" to localize the contents at the new site, the following error occurs:

Errors: 1: Localization failed; Source record contained a reference to an original default record (which is strange)!

If you set the content-elements l18n_parent to zero (in phpMyAdmin) it works.

You can reproduce the effect the following, shorter way:
1) Create an content element and localize it.
2) Move the localized version in the default-language column.
3) Press "copy default content elements" to localize it again.

Best regards,
Daniel

(issue imported from #M2142)


Related issues 4 (2 open2 closed)

Related to TYPO3 Core - Bug #19014: Copying Content Elements does not copy Language OverlaysClosedRupert Germann2008-06-25

Actions
Related to TYPO3 Core - Epic #101557: Translation Handling FindingsNew2023-08-03

Actions
Related to TYPO3 Core - Story #101561: DataHandler related translation issuesNew2023-08-03

Actions
Related to TYPO3 Core - Bug #102623: Switching l10n_parent to 0 triggers exceptionClosed2023-12-07

Actions
Actions

Also available in: Atom PDF