Bug #86059
closed
Wrong sorting for localized entries in page module with 8.7.16 and higher
0%
Description
With the release of 8.7.16, we get a regression in page module: The sorting for localized records will be determined using the sorting value from the localized record and the sorting from the default language will be ignored. The right way should be, to use the sorting from the default language record for the localized too.
Updated by
Updated by Riccardo De Contardi over 4 years ago
- Status changed from New to Needs Feedback
Is this issue still true on version 9.5.14 or the latest master (10.4.0-dev) ?
I tried a short test with the latest master:
1) Multilanguage page in ITA, ENG (id=1)
2) Created four content elements ("uno", "due", "tre", "quattro") in italian
3) Translate them ("Connected mode") in english: "one", "two" "three", "four" .
4) I used drag and drop to move around the four content elements in page > columns module
Results¶
the translated elements followed the same order of the ones in default language; the only thing I noticed is that on page> language module the page is not refreshed after the drag and drop, so the order in ENG seemed wrong; after a refresh of the page it became correct.
Am I doing something wrong? Or is a different test necessary?
Updated by Marc Hirdes almost 4 years ago
See workaaround here https://forge.typo3.org/issues/70154
Updated by Riccardo De Contardi over 3 years ago
- Related to Bug #70154: Extbase 'sorting' l10nmode added
Updated by Riccardo De Contardi over 3 years ago
- Related to Bug #93968: false order of localized CE in BE view / "Translate" button is shown but no translateable CE are available added
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 Bug #84951: Localization: Copying new record in existing localization has off-by-one issue added
Updated by Christian Kuhn almost 3 years ago
- Status changed from Needs Feedback to Closed
I'm quite certain we fixed that in recent v11 with one of the linked issues. I'll close the issue for now. If there is still an issue with broken language sorting in recent core v11, let's continue in a new issue.