TYPO3 Core

Denis Mir wrote in #note-8:

Error is still present in 12LTS. Even the `l10n_source` is not set at all.

That's correct, since you are not actually translating but just copying elements around.
If you want an l10n_source to be present, there has to be a real translation action before.
So you should use the translation modal and the so called "Free Mode" to get elements into another language.

IMHO the actual bug is, that you can copy elements from one language to another.

Problem for us was: We have English as primary language and then German. Nowadays, we write first the German content (and publish it) - then it is translated some weeks later to English (and published). As there is no "Translate back to default language) we have to copy these elements. And for "standard" elements it works (language id is adjusted) - but not for IRRE elements.

Of course, I suggested to our editors, first to set the content element in English (with German texts), if it is done, "translate" to German. Then only the content in English has to translated (but without touching the structure). But editors ...

And: English as default language was a conscious decision we made quite some years ago (which does not work anymore for us). And we need free mode, as on some pages the content structure is different for languages, so we have to go with free mode.

So: copying content elements is a use case. If this is "wrong", then the Core should prevent that (but then we need a translate to the default language). Or if it is possible: it should be fixed somehow.

To add: the fact that the parent element gets the correct language uid set, but not the IRRE childs is wrong in my pov. Which is what was described in this issue in the first place.

I agree with what Chris said. And it goes even further. We have free mode in some projects all around since the page content completely differs between the different locales.

And it always happens in these projects that we have e.g. Site A with Page B and Language de_DE and the editor copies one of the elements from this page to Site B, Page D and Language de_AT.

This action is possible currently and should be possible in the future. But it gets the described behavior. Wrong "sys_language_uid" for the IRRE stuff and even the related "sys_file_reference" entries.

So I would definitely say this is a bug and should be fixed. Just removing the feature is not an option.

Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/86773

Patch set 3 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/86773

Patch set 4 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/86773

Patch set 5 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/86773

Patch set 6 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/86773

I can reproduce this with "Text & Media" and "Media elements" [assets] field (sys_file_reference):

Steps to reproduce:

1. Create a "Text & Media"
2. Add a file in tab "Media" => "Media elements" [assets]
3. create translation for page
4. copy the content element to the translated page

Check in database: both records have sys_language_uid=0

select uid,pid,sys_language_uid,uid_foreign from sys_file_reference where pid=920 and not deleted;
+-----+-----+------------------+-------------+
| uid | pid | sys_language_uid | uid_foreign |
+-----+-----+------------------+-------------+
| 445 | 920 |                0 |         195 |
| 446 | 920 |                0 |         196 |
+-----+-----+------------------+-------------+

Patch set 7 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/86773

Patch set 8 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/86773

Patch set 9 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/86773

Patch set 10 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/86773

Patch set 11 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/86773

Patch set 12 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/86773

Patch set 13 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/86773

Patch set 14 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/86773

Patch set 15 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/86773

Patch set 1 for branch 13.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/87689