Project

General

Profile

Actions

Bug #52960

closed

FE Language overlay differs from BE

Added by Rainer Becker over 10 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Localization
Target version:
Start date:
2013-10-18
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.4
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

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 1 (0 open1 closed)

Related to TYPO3 Core - Bug #48673: Changed language overlay behaviour in TYPO3 6.*Closed2013-05-30

Actions
Actions #1

Updated by Mathias Schreiber about 9 years 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.

Actions #2

Updated by Rainer Becker about 9 years ago

Sorry for being unobjective.
Pleased to see that this issue and several other l10n related issues made it on the TYPO3 roadmap.

Actions #3

Updated by Susanne Moog over 8 years ago

  • Target version changed from 7.4 (Backend) to 7.5
Actions #4

Updated by Benni Mack over 8 years ago

  • Target version changed from 7.5 to 7 LTS
Actions #5

Updated by Mathias Schreiber over 8 years ago

  • Status changed from New to Closed

includeRecordsWithoutDefaultTranslation should solve your problem.

Keep in mind that we will change the behavior of "translations" vs. "independent content in a different language".

Actions

Also available in: Atom PDF