Bug #75851
closed
Extbase 110n_mode exclude + repository orderings
0%
Description
If you have translated TCA records and some fields in them with l10n_mode set to "exclude" (e.g. for a datetime field that doesn't need to be translated) and then an extbase repository ordering is based on this datetime field the order of the domain models returned by a repository finder method is not correct in a non-default language, as the l10n_mode set to "exclude" is not considered. Instead the sorting is done by the value of the field in the translated record, which can be filled with anything or not filled at all.
Expected behaviour: the datetime value from the default language record should be taken into account for the repository finder results ordering, as this is the only field the editor is able to edit and control the sorting with in this scenario.
If there is more info necessary to help to clear this up, please tell me.
Updated by Riccardo De Contardi about 7 years ago
- Category changed from Extbase to Extbase + l10n
Updated by Riccardo De Contardi about 7 years ago
- Related to Bug #62921: l10n_mode with relations does not work in Extbase added
Updated by Benni Mack over 5 years ago
- Status changed from New to Needs Feedback
- Target version deleted (
next-patchlevel)
Hey Matthias,
we fixed this in v8 with consistent values in l10n_mode=exclude values. Can you let us know that upgrading to any supported TYPO3 version solves your problem?
Thanks.
Benni.
Updated by Riccardo De Contardi over 5 years ago
- Status changed from Needs Feedback to Closed
No feedback since the last 90 days => closing this issue.
If you think that this is the wrong decision or experience the issue again and have more information about how to reproduce your problem on a recent TYPO3 version, please reopen it or ping me
thank you.