Project

General

Profile

Actions
Copy link

Bug #59971

closed

Reset languageMode query setting for child object queries in Extbase

Added by Alexander Stehlik over 10 years ago. Updated over 6 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Extbase
Target version:
-
Start date:
2014-06-29
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.4
Tags:
Complexity:
medium
Is Regression:
No
Sprint Focus:

Description

This behavior might be intended but it would be cool if it would be configurable somehow:

I have an Extbase domain model that can not be translated. It points to a child record that is translatable.

My setting config.sys_language_mode is set to "strict".

When the language changes and the child record is not translated the parent object property will be empty (because the original object is removed during language overlay).

Should the getPreparedQuery() method in the DataMapper also reset the language mode setting by default to not destroy relations by language overlay?

$query->getQuerySettings()->setLanguageMode(NULL);

Should this be configurable? Feedback is welcome:)

An actual example of this problem can be found in the cz_simple_cal Extension. The index entries point to single events that might be translated or not. How would you handle this with language mode "strict"? Enhance the event index query, so that only index records are found where a translation exists?

Related issues 2 (0 open — 2 closed)

Related to TYPO3 Core - Bug #50031: Ordering changes result if multilanguage contentClosed2013-07-15

Actions
Related to TYPO3 Core - Bug #82363: Make Extbase translation handling consistent with typoscriptClosedTymoteusz Motylewski2017-09-07

Actions
Actions
Copy link

Also available in: Atom PDF