Bug #52960
FE Language overlay differs from BE
| Status: | New | Start date: | 2013-10-18 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | Localization | Spent time: | - | |
| Target version: | 7.4 (Backend) | |||
| TYPO3 Version: | 6.2 | Is Regression: | No | |
| PHP Version: | 5.4 | Sprint Focus: | ||
| Complexity: |
Description
Content element record translations that have no default language record or where the default language is hidden are not shown in FE when fetched by TS (page.10 < styles.content.get). Extbase show this records and so does the backend in page module. There is no combination of sys_language_mode / sys_language_overlay which accomplishs this.
The default TYPO3 language overlay behaves not like I would expect. As a default, a record should be shown if
- there is a translation for the requested record OR
- the record is marked as "all languages"
In 15 multilanguage projects I made with TYPO3 there was not one case or client where this should be different. In my opinion one single option would be enough, namely: Should the default translation of a record be used, if there is no translation for the requested language?
It is disappointing that such an essential feature seems still not to work consistently (BE, TS, EXT) in the coming LTS release without helping out with the great (but not trivial) "tesseract" extension set.
(See #48673)
Related issues
History
#1 Updated by Mathias Schreiber 7 months ago
- Target version set to 7.4 (Backend)
Thanks for the motivational speech, I'm sure the team will appreciate it while working for free.
#2 Updated by Rainer Becker 7 months ago
Sorry for being unobjective.
Pleased to see that this issue and several other l10n related issues made it on the TYPO3 roadmap.