#82363Make Extbase translation handling consistent with typoscript
Description
Extbase rendering should give the same results as typoscript rendering.
Also settings used in TS and extbase should have the same meaning (languageMode, languageOverlay), as they are mixed up right now in extbase. As setting query languageOverlay has NO effect on queries, but
calling setLanguageMode(‘strict’) makes extbase pass “hideNonTranslated” to getRecordOverlays.
And “hideNonTranslated” is a value of the TS setting “sys_language_overlay” and has nothing to do with languageMode.
Reviews 4
Related issues 11
- Bug #47192setRespectSysLanguage(FALSE) doesn't prevent language overlay when fetching localized objects
- Feature #51250getObjectByIdentifier should use defaultQuerySettings from repository
- Bug #57272Extbase doesn't handle FAL translations correctly
- Bug #57272Extbase doesn't handle FAL translations correctly
- Bug #59971Reset languageMode query setting for child object queries in Extbase
- Bug #63031Weird Translation behaviour in extbase
- Bug #77298Wrong language overlay logic in extbase
- Bug #79934Localized one/many to many not mapped correctly
- Task #82187Provide functional tests showing translated tt_content + FAL
- Task #82298Functional tests for tt_content with FAL rendering in extbase
- Bug #88886DataMapper: Consider languageOverlayMode "hideNonTranslated" when getting relations using consistentTranslationOverlayHandling