Bug #90261
open
fallbackType: fallback renders default language content although there is free mode content available
0%
Description
A language with this site config:
fallbackType: fallback fallbacks: '0'
Tested with this simple TypoScript rendering
page = PAGE page.100 =< styles.content.get
yields default language content although the requested language has content in "Free mode" (meaning: no l18n_parent). In "Connected Mode" there is no problem.
- interestingly, using the vhs-ViewHelper `v:content:render` yields all content doubled (translated + default language)!!
Updated by
Updated by Sebastian Schrama over 4 years ago
Any updates here? I'm having exactly the same issue and we really need the free mode in combination with content fallback.
Updated by Marieke de Bruin about 4 years ago
I'm having the same problem in CMS10
Updated by Jonas Eberle almost 4 years ago
I was interested in what was communicated about `free content` and `fallbackType: fallback`. Some resources:
- For integrators: https://docs.typo3.org/m/typo3/guide-frontendlocalization/master/en-us/LocalizedContent/Index.html
Mentions a `free content strategy` which I cannot find any other references to. `fallbackType: fallback` is in the section "Connected content". - For integrators: https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/ApiOverview/SiteHandling/AddLanguages.html#fallbacktype
- For editors: https://docs.typo3.org/m/typo3/tutorial-editors/master/en-us/Languages/Index.html
`free content`/`connected content`/`mixed content` is not mentioned there.
Although not clearly stated, this might imply that it was thought as a site-wide choice. In that case implementation would be lacking since editors are able to create content free/connected/mixed.
Yet since documentation is not very clear about it, it might give us a chance now to define how we would like to handle it without much risk to contradict ourselves.
Updated by David Henninger almost 4 years ago
To me, the name "fallback" with its description "Show default language if no translation exists" indicates, that once there is a translation for a page (or rather content) available, it shows just that, otherwise, follow the "fallbacks" order and show the first existing translation for the content.
This seems to work well when translation is in "connected mode".
However, with a translation in "free mode", unique content exists for each language and there is no linking between content elements.
As the content of translated pages are not linked to contents of the base language, fallback mode instead ignores all the custom language specific content elements and just shows the contents of the base language.
What I would have expected, was that the unique language specific content will be shown and nothing of the base language, unless the page is untranslated (or in mixed mode, with some contents referencing the base language).
Example:
- Base language is English
- Translation is German and its content in free mode
- news extension has mostly English articles, some of which also available in German (linked via l10n_parent)
- A shortcut element within the German translation points to an English content element of the base language
| Typo3 | fallbackType | page content | news articles | shortcut element |
|---|---|---|---|---|
| v8 | German | all articles (preferably in German) | displayed | |
| v9 | strict | German | only German articles | missing |
| v9 | fallback | English | all articles (preferably in German) | displayed (original) |
| v9 | free | German | only German articles | displayed |
Updated by Jonas Eberle almost 4 years ago
- Assignee deleted (
Jonas Eberle)
After talking to Benni about that it became clear to me also that the current implementation of record translation is holding us back in several places. I hope I understood him correctly.
One idea would be to get rid of overlays (languages + workspaces) altogether and have any single database record contain all the necessary state at all times. So instead of doing all the heavy lifting while querying pages/CEs it would be beneficial to do the work during creation/updates already, eventually updating/adding several records at once (if the editor/integrator chose some "connected mode" for fields/relations or records). That would also include to get rid of the infamous "All languages [-1]" setting which is a burden in several places.
That said, I am not aware of an initiative of developers in that direction yet.
I would still consider this a bug in v9 and v10 and maybe this very symptom might be easily fixable.
Yet for the time being, I will not use language fallbacks at all and hide the language field for editors.
Updated by Frank Gerards over 3 years ago
to wrap things up for developers: Language handling between Site Module and page translation in Free Mode is broken. There is yet no way to have FallbackType "Fallback" and page fallback to another language rather than Default language in Free Mode handled correctly by the core. I wouldnt recommend TYPO3 v10 then to customers using this combination.
Updated by Thomas Oliver Moll over 2 years ago
Is there any development on this?
We are still on v10 is this addressed in v11?
Updated by Benjamin Franzke over 2 years ago
@Thomas Oliver Moll:
Currently no development in core, also not fixed in v11.
As a workaround we've written a middleware to switch dynamically to fallbackType=free (for the current request) when there is any unconnected translation on the current page:
https://github.com/qbus-agentur/typo3-dynamic-language-mode
Might be of help if you need a quick fix.
Updated by Sven Burkert over 2 years ago
- TYPO3 Version changed from 9 to 10
- Tags changed from languages to languages, language handling, free mode, connected mode
interestingly, using the vhs-ViewHelper `v:content:render` yields all content doubled (translated + default language)!!
Content is also doubled in other circumstances, e.g. when using EXT:bootstrap_package :(
Updated by Anonymous over 2 years ago
- Related to Bug #88965: Siteconfigurations fallbackType "strict" shows free contents added
Updated by Michael Stein about 2 years ago
- TYPO3 Version changed from 10 to 11
Hi there,
For my latest project I did and xclass of the record overlay method in the page repository:
https://extensions.typo3.org/extension/mst_contentfallback
Updated by Gerrit Code Review over 1 year ago
- Status changed from New to Under Review
Patch set 1 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/78474
Updated by Astrid Haubold about 1 year ago
- Related to Story #101565: Frontend related translation issues added