Feature #17547
closedIssue with Multilanguage-Pages and Content-Elements enabled for "All" languages
0%
Description
Hello,
i recently build a multi-language enabled Typo3-Page basing on the "One Tree fits all" concept. While building page-contents I figured out that contents enabled to be shown for "All" languages are not shown in Backend (Page-Contents) anymore. These Contents are only shown in Listing-Mode.
I would prefer to enable that these contents are also shown in the regular content-page to have an overview of all contents included in the FE-Page. I didn't find any switch or option to enable this. So I would like to know if this feature is planned to be integrated in one of the future builds or if it is possible to override the language_uid-flag for the selects in these backend-module (f.e. by any extension hack?).
Best Regards
Gabriel Kaufmann
(issue imported from #M6186)
Updated by Christian Kuhn almost 16 years ago
Confirmed:
All content elements set to Language = [All] are not shown in the default page module.
Is there any TSconfig switch I might have missed that should be used to show these items in classic Web->Page?
Updated by Christian Kuhn almost 16 years ago
Here is the Page TSconfig trigger, the [All] elements will be shown in the default language column:
mod.web_layout.defLangBinding = 1
From the documentation:
doc_l10nguide:
When using language binding combined with “config.sys_language_overlay = hideNonTranslated” there is a special significance of the language value “[All]” (technically the -1 value): These elements will not be hidden in the translation - and they are not meant to be translated although you can choose to do so.
doc_core_tsconfig:
If set, translations of content elements are bound to the default record in the display. This means that within each column with content elements any translation found for exactly the shown default content element will be shown in the language column next to.
This display mode should be used depending on how the frontend is configured to display localization. The frontend must display localized pages by selecting the default content elements and for each one overlay with a possible translation if found.
So it doesn't make much sense to use the [All] setting and not enable language binding. Maybe the page module could still be improved in this regard, but this would be another issue with some good proposal on what should be done.
Updated by Christian Kuhn almost 16 years ago
Resolved with no change required for now.
This issue might be set as related to a new one if someone comes up with an idea on how to improve the page module it this regard, with the different TS / Page TSconfig switches in mind.