Bug #86712
closedconfig.sys_language_overlay has no effect
100%
Description
Hi,
the Typoscript setting config.sys_language_overlay seems to have no effect anymore with the new Context and LanguageAspect.
Even though LanguageAspect has a separate constructor parameter for setting the overlay type, it is actually never called with that parameter. Therefore always the fallback value of includeFloating is used. When setting the overlay mode for queries in repositories manually, the overlay works as intended.
There even is a LanguageAspectFactory which would take the Typoscript configuration into account, but that class is only used in the FrontendController.
Regard,
Philipp
Files
Updated by Philipp Seiler about 6 years ago
- Related to Bug #86595: No Language Fallback added
Updated by Tymoteusz Motylewski about 6 years ago
- Category changed from Localization to Site Handling, Site Sets & Routing
Updated by Sven Juergens about 6 years ago
same problem here.
if I use SiteHandling I will no longer see translations in FreeMode regardless of language fallback modes
Updated by Sven Juergens about 6 years ago
For me it was about the standard output of tt_content elements.
"Problem" was that I got the content with the standard query styles.content.get. In that case there was no translated content in free mode, if SiteHandling was used.
if I extend the query of styles.content.get to
10 <styles.content.get
10.select.includeRecordsWithoutDefaultTranslation = 1
the output of tt_content works again...
maybe it will help other seekers
Updated by Philipp Seiler about 6 years ago
I've included content via the Typoscript CONTENT object (as far as I remember styles.content.get is just an alias for CONTENT), and it still doesn't work.
temp.content0 = CONTENT temp.content0 { table = tt_content wrap = | select { where = colPos = 0 orderBy = sorting languageField = sys_language_uid includeRecordsWithoutDefaultTranslation = 1 } }
Note: In my case I'm talking about News-Records, not standard tt_content. includeRecordsWithoutDefaultTranslation doesn't work for standard content elements for me either.
Maybe my page configuration is wrong?
config { sys_language_uid = 0 sys_language_overlay = 1 sys_language_mode = content_fallback;1,0 }
Updated by Susanne Moog about 6 years ago
- Sprint Focus set to On Location Sprint
Updated by Sebastian Mazza almost 6 years ago
I can confirm that the config.sys_language_overlay is totally useless in TYPO3 9.5 if a Site-Configuration (typo3conf/sites/xxxx) is used. => I'm not able to display any non translated tt_content record in the FE.
Updated by Sebastian Mazza almost 6 years ago
- File RequestMiddlewares.php RequestMiddlewares.php added
- File LanguageOverlayFixer.php LanguageOverlayFixer.php added
As a workaround for this problem I have implemented a Middleware that sets the overlayType
of the LanguageAspect
to "mixed".
Updated by Gerrit Code Review over 5 years ago
- Status changed from New to Under Review
Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/60367
Updated by Gerrit Code Review over 5 years ago
Patch set 1 for branch 9.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/60456
Updated by Benni Mack over 5 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 064f90432058b00a1fcc484de02e9864672dba25.
Updated by Benni Mack about 3 years ago
- Related to Bug #88367: Improve option names of "Fallback Type" in the sites configuration added