Bug #81328
open
Translation didn't sort Elements correct.
0%
Description
This bug was found in TYPO3 7.6 and reproduced now in TYPO3 8.7
Whats the Bug¶
The bug is that the sorting of content elements can be different between the original language and a translation.
How can I reproduce the bug¶
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
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.
8.) Translate now the Content Element B on Page B
Now the Content Element A and the Content Element B do not have the same sorting in both languages. Because sorting in the foreign language is not available you can not sort the elements in the correct order.
This behaviour was tested on TYPO3 7.6.16 and 8.7.17
A video of the reproduction in TYPO3 8.7 can be found in file section below.
How could this Bug be fixed¶
In my opinion we are having two possible solutions for this way
1. Check at every translation the original sorting. And Update it if nessecary for all other languages.
2. Don't block the sorting function, when you translate content elements.
Files
Updated by Mona Muzaffar almost 7 years ago
- Related to Bug #78220: Translate mode copy does not respect order added
Updated by Markus Gehrig over 5 years ago
- File typo3_bug_2.mov typo3_bug_2.mov added
- File Bildschirmfoto 2018-10-30 um 15.17.01.png Bildschirmfoto 2018-10-30 um 15.17.01.png added
- Description updated (diff)
- TYPO3 Version changed from 7 to 8
Bug still exists in TYPO3 8.7
Updated by Markus Gehrig over 5 years ago
- Related to Bug #86709: TYPO3 Translation missleading List of content which should be translated added
Updated by Markus Gehrig over 5 years ago
- Related to Bug #86640: Translations are created on the wrong page if translations were moved previously (severe) added
Updated by Riccardo De Contardi about 4 years ago
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.
Updated by Dominic Lehle almost 3 years ago
- TYPO3 Version changed from 8 to 10
- PHP Version set to 7.4
This issue still remains in Typo3 10.4.17 and is reproducible. Is there anything done regarding this or an update?
Updated by Marco H over 2 years ago
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.
Updated by Christian Kuhn about 2 years ago
- Related to Bug #83469: Translation of translations break sorting in tt_content added
Updated by Christian Kuhn about 2 years ago
- Related to Bug #83079: wrong sorting of content elements when translating using non-default-language CEs as source added
Updated by Christian Kuhn about 2 years ago
- Related to Task #85300: Improve record sorting performance added
Updated by Christian Kuhn about 2 years ago
- Related to Bug #84951: Localization: Copying new record in existing localization has off-by-one issue added
Updated by Christian Kuhn about 2 years ago
- Status changed from New to Needs Feedback
Hey. I'm relatively confident this has been fixed meanwhile - at least v11 shouldn't show this behavior anymore. Can you confirm?
Updated by Riccardo De Contardi over 1 year ago
I can confirm the issue on 11.5.16 and 12.0.0-dev with the same test I reported on my comment 9
Updated by Melissa Eisele about 1 year ago
- TYPO3 Version changed from 10 to 11
- PHP Version changed from 7.4 to 8.2
Riccardo De Contardi wrote in #note-17:
I can confirm the issue on 11.5.16 and 12.0.0-dev with the same test I reported on my comment 9
Hi,
this bug still exists on our projects (TYPO3 v11.5.23) and we hope that an official bugfix will be provided. The workaround in comment #9 would take a lot of time for editors.
Thank you in advance!
Updated by Clemens Riccabona about 1 year ago
I can also confirm on 11.5.23 and PHP 8.2
Bug still persistent.
Updated by Riccardo De Contardi 3 months ago
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