Project

General

Profile

Actions

Bug #75851

closed

Extbase 110n_mode exclude + repository orderings

Added by Matthias Krappitz about 8 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Extbase + l10n
Target version:
-
Start date:
2016-04-21
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
7
PHP Version:
7.0
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

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.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #62921: l10n_mode with relations does not work in ExtbaseClosed2014-11-13

Actions
Actions

Also available in: Atom PDF