no sorting in "Localization view" (with own records)
|Priority:||Should have||Due date:|
I made a new extension with an own datatable.
this table includes sorting and languagedependency
In the BE I can create new records and localize them.
If I then change the sorting with "Localization view" (e.g. moving the last record-set (master and localized records) to the top) only the master-records get a new sorting-value. The localized records didn't change their sorting-value.
This results in a strange behavior in a FE-Plugin which displays the records in a list (with the inherited methods): the order for the records is different in every language.
(issue imported from #M2650)
|related to Core - Bug #16845: Incorrect values of colPos, sys_language_uid and sorting ...||Resolved||2007-01-09|
Updated by TL over 2 years ago
The Bug not only happens when using custom datatables but also when localizing core content elements. (Typo3 4.4.4)
Updated by Thierry Brodard over 2 years ago
I think now it's a "normal" feature to first fetch all records from the default language, included the sorting, and then localize each of them.
I do so now in my extensions. It looks "strange" but it works.
The only "problem" is for performance: if you have 100 records to read, the amount of queries will be 101 (one for all records of the default language, and 100 for each localisation).
Updated by Matthias Krappitz over 2 years ago
I still think this is a bug. Because sometimes the sorting value of localized child records gets updated when sorting records up or down in list module and sometimes it does not. It sill occurs in 4.4.6.
Updated by Stanislas Rolland over 2 years ago
Please test patch attached to issue #16845 with TYPO3 4.5 or current trunk.
Updated by Stanislas Rolland 7 months ago
- Target version deleted (
- TYPO3 Version changed from 3.8.0 to 4.5
- PHP Version deleted (
Is this still an issue in current stable releases?