#90261fallbackType: fallback renders default language content although there is free mode content available
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)!!
Reviews 1
Related issues 4
Files 3
History 2026
Show 1 earlier messages
-
Susanne Moog changed category <span data-processor="relativetime" data-value="2020-03-26T15:37:51+00:00" > 03/26/20, 15:37 </span>
-
Sebastian Schrama commented <span data-processor="relativetime" data-value="2020-05-28T21:22:12+00:00" > 05/28/20, 21:22 </span>
-
Marieke de Bruin commented <span data-processor="relativetime" data-value="2020-09-23T14:07:06+00:00" > 09/23/20, 14:07 </span>
I’m having the same problem in CMS10
-
Jonas Eberle changed assigned to Jonas Eberle <span data-processor="relativetime" data-value="2020-12-03T09:15:47+00:00" > 12/03/20, 09:15 </span>
-
Jonas Eberle commented <span data-processor="relativetime" data-value="2020-12-05T10:47:30+00:00" > 12/05/20, 10:47 </span>
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.
- For integrators: https://docs.typo3.org/m/typo3/guide-frontendlocalization/master/en-us/LocalizedContent/Index.html
-
David Henninger commented <span data-processor="relativetime" data-value="2020-12-09T15:51:53+00:00" > 12/09/20, 15:51 </span>
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.
This new language implement comes with a regression, as it cannot currently reproduce the behavior of Typo3 v8.
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 -
Jonas Eberle commented and changed removed the assignee <span data-processor="relativetime" data-value="2021-01-09T11:11:44+00:00" > 01/09/21, 11:11 </span>
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.
-
Frank Gerards commented <span data-processor="relativetime" data-value="2021-08-03T01:12:13+00:00" > 08/03/21, 01:12 </span>
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.
-
Thomas Oliver Moll commented <span data-processor="relativetime" data-value="2022-02-23T11:06:01+00:00" > 02/23/22, 11:06 </span>
Is there any development on this?
We are still on v10 is this addressed in v11? -
Benjamin Franzke commented <span data-processor="relativetime" data-value="2022-02-23T11:18:12+00:00" > 02/23/22, 11:18 </span>
@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-modeMight be of help if you need a quick fix.
-
Sven Burkert commented and changed TYPO3 Version
910 Tagslanguageslanguages, language handling, free mode, connected mode <span data-processor="relativetime" data-value="2022-05-06T10:59:50+00:00" > 05/06/22, 10:59 </span>> 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 :(
-
Anonymous changed Related to #88965 <span data-processor="relativetime" data-value="2022-05-09T05:45:35+00:00" > 05/09/22, 05:45 </span>
-
Michael Stein commented and changed TYPO3 Version
1011 <span data-processor="relativetime" data-value="2022-09-02T06:53:42+00:00" > 09/02/22, 06:53 </span>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 -
Gerrit Code Review pushed patch set 1 for main to change 78474 status
NewUnder Review <span data-processor="relativetime" data-value="2023-04-05T10:52:48+00:00" > 04/05/23, 10:52 </span> -
Astrid Haubold changed Related to #101565 <span data-processor="relativetime" data-value="2023-10-20T08:24:34+00:00" > 10/20/23, 08:24 </span>
-
Gerrit Code Review pushed patch set 2 for main to change 78474 <span data-processor="relativetime" data-value="2024-12-12T09:03:38+00:00" > 12/12/24, 09:03 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 78474 <span data-processor="relativetime" data-value="2025-01-02T20:47:54+00:00" > 01/02/25, 20:47 </span>
-
Benni Mack commented and changed status
Under ReviewNeeds Feedback <span data-processor="relativetime" data-value="2025-03-22T20:12:45+00:00" > 03/22/25, 20:12 </span>Catching up now in 2025.
Can somebody enlighten me on what is missing?
Here is the current status that is in place (you can use this for reference and documentation and hanging on the walls):
Since TYPO3 v12, there is a method called PageRepository->getLanguageOverlay() that takes care of everything in the frontend. It does multi-step fallback, works with extbase and regular content. It is built to last, it is tested well enough and handled properly.
Some information on site handling and the definition of “free mode” vs. “fallback” mode:
In TYPO3 v9, I introduced several options to ensure that we do not need to define everything in TypoScript anymore. That’s why we have site configuration so it is available in Frontend in Backend.
Some more definitions:- -1 = ALL Languages, always is a mess regarding sorting, always. I recommend to use it with care
- Floating Records: Records that do not have a l18n_parent = no pendant in default language (l18n_parent=0 but sys_language_uid > 0)
- Overlay mechanism: Fetch records in default language, then check if there is a “translation” in language 5 -> that’s the “overlay” because the UID of the default language is kept in the result record.
- Multi-level fallback: Get all records in Language = 0, When not available in language 5, check for e.g. language 3 etc. (based on your fallback Chain)
- l10n_source was introduced in v8 (not by me) to overcome something completely else – not related to rendering. l10n_source is only relevant / evaluated in page module (= thus, for tt_content) currently
Specialities to “pages” table:
- “1” does not exist there (on purpose)sorting is synced 1:1 between default language and all translations
- there is a special field called l10n_cfg which is horrific, and only there because we had “pages” and then “pages_language_overlay” back in 2003.
- l10n_source and l10n_parent are always the sameAnd now to the Site configuration options:
We have three options when rendering a website in e.g. language ID 5 (Spanish):
- “free”: give me all records in language=5 directly – NO OVERLAYS, no default records. It’s the fastest – but there is a mess with records with sys_language_uid=“1” and also when starting to have relations.“strict”: give me all records in language=0 and “1”, make overlays in language ID 5, and if there is no overlay, do NOT render the ones in the default language“fallback”: give me all records in language=0 and “-1”, make overlays in language ID 5, if there is no overlay, check the fallback chain, and render the ones that exist (usually default language is the last resort)ALL of the modes include “floating records”, always. This is by design, and the previous feedback I encountered in the past years tells me, that this is a good practice.
When thinking logically here, “fallbacks” (either fallback or strict) are actually overlays but seen from the other side – from default language = 0 here. That implies the following rules by code law:
- Sorting is based on the initial query of language 0 and “1” records, “-1” records just stay as they are, where the other records are “overlaid“When a “default language” record is hidden (or starttime in future etc), then it is not returned from the SQL query in the first place. Thus, disabled, starttime, endtime for overlays always follow the default language. This is the reason why these “systemFields” should always be l10n_mode=exclude. And you can’t change anything bout it (except – “free”?).As result, getting back to the Page Module, where somebody else came up with similar terms, and only kept this in Page module, not in list module, element browser, FormEngine etc… Page Module:
- “Free Mode” – All content elements of a given language on this page have l10n_parent=0
- “Connected Mode” – All content elements of a given language on this page have l10n_parent>0 – no sorting possible (see above why)
- “Mixed Mode” – Some have l10n_parent>0, others have l10n_parent=0So maybe you understand, why all of this naming confusion comes from.
I would love if somebody would finally go ahead and make a new page module, that actually shows the BE as it would be in the frontend.
Some more things to fix:
- Get rid of sys_language_uid = “1“Fix sorting” by using sorting “namespace” on a per-partition basis such as “language” or “colPos“
- Connect or re-connect elements to become “Connected” again via GUIFun Fact: Because of a typo ;) the tt_content table has the DB field name “l18n_parent” (i10n for internationalization vs. l10n for localization) whereas the others use “l10n_parent” as field name.
And for everyone who read until here: I would HIGHLY recommend to not just use tt_content as a IRRE child element somewhere (e.g. in another content element) due to colPos + sorting issues. Have a nice evening.
-
Gerrit Code Review pushed patch set 4 for main to change 78474 status
Needs FeedbackUnder Review <span data-processor="relativetime" data-value="2025-03-22T20:14:30+00:00" > 03/22/25, 20:14 </span> -
Gerrit Code Review pushed patch set 5 for main to change 78474 <span data-processor="relativetime" data-value="2025-03-25T14:12:38+00:00" > 03/25/25, 14:12 </span>
-
Benni Mack changed Related to #89528 <span data-processor="relativetime" data-value="2025-03-27T13:54:11+00:00" > 03/27/25, 13:54 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 78474 <span data-processor="relativetime" data-value="2025-03-28T20:06:44+00:00" > 03/28/25, 20:06 </span>
-
André Buchmann commented and changed attached clipboard-202503282201-oxoof.png attached clipboard-202503282201-4zlfk.png attached clipboard-202503282201-1jwtn.png <span data-processor="relativetime" data-value="2025-03-28T21:05:00+00:00" > 03/28/25, 21:05 </span>
Thx @benni for tackling this topic
clipboard-202503282201-oxoof.png
Fallback behaviour before patch:
clipboard-202503282201-1jwtn.pngFallback with patch:
clipboard-202503282201-4zlfk.pnglanguages: - title: English enabled: true languageId: 0 base: / locale: en_US.UTF-8 navigationTitle: English flag: us typo3Language: default iso-639-1: en hreflang: en-us direction: ltr websiteTitle: '' - title: Danish enabled: true base: /da/ typo3Language: da locale: da_DK.UTF-8 iso-639-1: da websiteTitle: '' navigationTitle: '' hreflang: da-dk direction: '' fallbackType: strict fallbacks: '' flag: dk languageId: 1 - title: German enabled: true base: /de/ typo3Language: de locale: de_DE.UTF-8 iso-639-1: de websiteTitle: '' navigationTitle: '' hreflang: de-de direction: '' fallbackType: fallback fallbacks: '0' flag: de languageId: 2 -
Benni Mack commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2025-03-29T11:00:11+00:00" > 03/29/25, 11:00 </span>Applied in changeset commit:49756268f584c353c9b87d8337d16bda48dd2641.
-
Benni Mack changed Related to #88966 <span data-processor="relativetime" data-value="2025-04-03T13:36:07+00:00" > 04/03/25, 13:36 </span>
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2025-12-02T14:36:46+00:00" > 12/02/25, 14:36 </span>
Any updates here? I’m having exactly the same issue and we really need the free mode in combination with content fallback.