Bug #78220
closedTranslate mode copy does not respect order
0%
Description
When translate content, the order of the source language should be respected.
It is cumbersome for editors to rearrange the content elements.
- Go to a an empty page and create on content element
- Translate the page
- Translate the content element with copy-mode
- Create 2-3 new content elements in default language
- Translate the content again
You will notice that the localized content is in random order.
Files
Updated by Remo H. about 8 years ago
- File LocalizeCopyMode.png LocalizeCopyMode.png added
When translate content, the order of the source language should be respected.
It is cumbersome for editors to rearrange the content elements.
Steps to reproduce:
- Create a new page and a translation of it
- Create a content element with header "b"
- Translate element with copy mode
- Create below first a new content element "a", then "d" and "c": You should have following order now "b,a,d,c"
- Move "a" with drag'n'drop above "b"
- Move "d" with drag'n'drop bellow "c": You should have following order now "a,b,c,d"
- Translate elements with copy mode
You will notice, the elements are not in the expected order.
Though it is in "copy", as an editor I expect that the order get respected as much as it is possible.
This means a content element inserted on position 2, should be at position 2 when translated if possible.
Updated by Daniel Maier about 8 years ago
- Target version set to Candidate for patchlevel
Updated by Markus Mächler about 8 years ago
i tested your case and could not reproduce the behaviour. I got the correct ordering.
we recently had a similar issue, which was found to be due to a localized record being nested in an element of the default language.
it seems the translation handling in https://github.com/TYPO3/TYPO3.CMS/blob/TYPO3_7-6/typo3/sysext/backend/Classes/Controller/Page/LocalizationController.php is very error-prone
Updated by Mona Muzaffar over 7 years ago
- Related to Bug #81328: Translation didn't sort Elements correct. added
Updated by Riccardo De Contardi almost 7 years ago
I tried to reproduce on both 8.7.10 and 9.2.0-dev (latest master) using the test reported on comment 1
Results: on both, the final order of the translated content elements is: A,C,D,B
Updated by Riccardo De Contardi over 4 years ago
- Status changed from New to Needs Feedback
This issue is no more reproducible on both 9.5.14 and 10.4.0-dev (latest master), I tried with the test proposed on comment 1:
Create a new page and a translation of it
Create a content element with header "b"
Translate element with copy mode
Create below first a new content element "a", then "d" and "c": You should have following order now "b,a,d,c"
Move "a" with drag'n'drop above "b"
Move "d" with drag'n'drop bellow "c": You should have following order now "a,b,c,d"
Translate elements with copy mode
Result:
the order of the translated element is A,B,C,D
Is a different test necessary or this issue can be considered solved?
Updated by Christian Kuhn almost 3 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 almost 3 years ago
- Related to Bug #83469: Translation of translations break sorting in tt_content added
Updated by Christian Kuhn almost 3 years ago
- Related to Task #85300: Improve record sorting performance added
Updated by Christian Kuhn almost 3 years ago
- Related to Bug #84951: Localization: Copying new record in existing localization has off-by-one issue added
Updated by Christian Kuhn almost 3 years ago
I'm pretty confident this has been solved meanwhile: There were a couple of fixes in this area and we also didn't see fresh reports here. Closing for now.
Updated by Riccardo De Contardi almost 3 years ago
- Status changed from Needs Feedback to Closed
- Target version deleted (
Candidate for patchlevel)
Closed for now. If you think this is the wrong decision, please reopen or open a new issue with a reference to this one.