Bug #62550
closed
activated defLangBinding: Content Elements that exist only in translation are not displayed at all
Added by Andreas Allacher about 10 years ago.
Updated about 6 years ago.
Category:
Backend User Interface
Description
With activated defLangBinding setting content elements that only exist in the translation are not displayed at all.
The problem seems to be
if (!$lP && ($this->defLangBinding || $row['sys_language_uid'] != -1)) {
and
$defLangBinding[$key][$lP][$row[$lP ? 'l18n_parent' : 'uid']] = $singleElementHTML;
Instead of checking regarding language "$lP", it would be better to check if the l18n_parent is set for the corresponding row.
Of course, one also needs to modify getNonTranslatedTTcontentUids method accordingly
Files
Related issues
1 (1 open — 0 closed)
- Category set to Backend User Interface
- TYPO3 Version changed from 6.2 to 7
In 7 LTS (and current master) the issue can be reproduced as following:
- Create a page with at least one alternative language
- Copy content to the alternative language (not translate, but copy)
- enable mod.web_layout.defLangBinding = 1
- Go to page module in language mode
Still reproducible in latest master 9.0.0-dev
- Related to Bug #81753: Content element translations dissapear in page module after move to another column added
- Status changed from New to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Under Review
Here are my results when testing this change in TYPO3v8 (8.7.15): when activating the defLangBinding
option, translated content is invisible as described in the report. However, this is not fixed even after applying the change. But now even the container for the content element is invisible.
- Status changed from Under Review to Resolved
- Status changed from Resolved to Closed
Also available in: Atom
PDF