#48673Changed language overlay behaviour in TYPO3 6.*
Description
Create this records:
- 0A All languages - 1A Default Language - 1B Default Language translated - 2A Default Language (hidden) - 2B Default Language translated - 3A Default Language - 3B Default Language translated (hidden) - 4A Default Language - 5B Default Language translated
Setting: sys_language_overlay = hideNonTranslated
In FE / default language / TYPO3 V6 these will be shown:
0A, 1A, 3A, 4A (which is correct in my opinion)
In FE / other language / TYPO3 V6 these will be shown:
0A, 1B (which is incorrect in my opinion; 2B and 5B are missing)
In FE / other language / TYPO3 V4.5 these will be shown:
0A, 1B, 5B (which is still incorrect in my opinion; 2B is missing)
Is this change intended? If yes: Where is this documented? This is a major change in one of the most crucial enterprise features of TYPO3…
Btw: If records are fetched via extbase in V6 all translated records (0A, 1B, 2B, 5B) show up.
In TYPO3 6.1 the behaviour is unchanged.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 11
- Bug #17354fallback for menus. "content_fallback;1,0" has no affect for page records (e.g. menu)
- Bug #19114sys_language_mode content_fallback with a defined fallback chain does not output expected fallback content
- Feature #33734Domain - Language mapping
- Feature #34823Remove language "default" from Alternative Page Language Records
- Bug #39798Language and colpos changes on re-ordering of Content Elements
- Bug #52960FE Language overlay differs from BE
- Bug #60052sys_language_mode=content_fallback only supports language uid 0 as fallback
- Bug #63684sys_language_uid and sys_language_content are always the same
- Task #69966Integrate localization and fallback resolving in PlainDataResolver
- Bug #69999Cannot create CE without default language
- Bug #56351view page in another language than default language from Backend is incorrect