Actions
Bug #88372
closedExtbase QuerySettings ignores SiteConfiguration language settings
Status:
Closed
Priority:
-- undefined --
Assignee:
-
Category:
Extbase + l10n
Target version:
-
Start date:
2019-05-16
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
9
PHP Version:
7.2
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
Precondition:
- Default Language in EN.
- Russia is configured as static (fallbackType)
languages:
-
title: 'Global (English)'
enabled: true
languageId: '0'
base: /
typo3Language: default
locale: en_UK.utf-8
iso-639-1: en
navigationTitle: 'EN'
hreflang: en-GB
direction: ltr
flag: england
overlayType: 'off'
-
title: Russian
enabled: true
languageId: '1'
base: /ru/
typo3Language: ru
locale: ru_RU.utf-8
iso-639-1: ru
navigationTitle: Russina
hreflang: ru
direction: ltr
fallbackType: strict
flag: ru
In general, all pages and content elements are rendered correctly as configured (strict mode, no fallback).
But with records in extbase context (eg news record) which exists only in russia, I do not get any records in the frontend unless there already exists a default record of it.
A quickfix for was, to override the NewsRepository and add the following line to the querySettings:
$query->getQuerySettings()->setLanguageOverlayMode(false);
Updated by Christian Eßl about 5 years ago
- Category changed from Extbase to Extbase + l10n
Updated by Riccardo De Contardi almost 5 years ago
Is this one related? #87160 Or even the same issue?
Updated by Georg Ringer over 4 years ago
- Related to Bug #87160: Creating site config breaks language processing in news and vhs extensions added
Updated by Georg Ringer over 4 years ago
- Related to Bug #89295: Typo3QuerySettings set as DefaultQuerySettings in a Repositories initializeObject Method are not honored added
Updated by Christian Kuhn almost 2 years ago
- Status changed from New to Closed
I hope it's ok to close here since there hasn't been any further feedback for a long time.
Actions