TYPO3 Core

This issue is still reproducible on 9.5.14 and 10.4.0-dev with the same steps reported on the description; I'll just add a couple of details to make them more clear

1.) Create a new Page A
2.) Create a new Content Element A on Page A
3.) Translate the Page A and the Content Element A to another Language use "connected mode" (translate)
4.) Create a new Page B
5.) Create a new Content Element B on Page B
6.) Translate the Page B to the same Language to which you translate Page A. Do not translate any Content Element now only the Page.
7.) Copy the Content Element A from Page A to Page B. The Translation of the Content Element A should be copied with the default Element. be sure to copy the element A after element B
8.) Translate now the Content Element B on Page B

Result:

default language order of elements: B,A

translated order of elements: A,B

Important!!¶

Because sorting in the foreign language is not available you can not sort the elements in the correct order.

It is not completely correct: on version 9.5.14 and 10.4.0-dev you can use the list view to reorder the elements B,A into A,B and then again into B,A - this operation will make the translated elements gain the correct order.

Still an issue in 10.4.18

Regarding solutions:
I don't think sorting should be enabled in connected mode, that's what free mode is for (imo).

The way I see it, it needs to be implemented like:

• translation of language in "connected mode" is triggered -> update all in this language by sorting value of elements in default language
• any kind of sorting update in default language is triggered -> check if "connected mode" languages exist and update all in this language by sorting value of elements in default language

It is weird how this bug seems to exist for years, seems like a problem that would happen regularly with multi language pages.

I can confirm the issue on 11.5.16 and 12.0.0-dev with the same test I reported on my comment 9

I can also confirm on 11.5.23 and PHP 8.2
Bug still persistent.

I can confirm the issue on 11.5.34, 12.4.10 and 13.0.0-dev latest main with the same test I reported on my comment 9