Bug #21869
closed
t3lib_tceforms does not respect mod.SHARED.disableLanguages
Added by Xavier Perseguers over 14 years ago.
Updated almost 10 years ago.
Description
When a flexform does not disable inline translation (that is it enables it):
<meta>
<langDisable>0</langDisable>
</meta>
all languages are made available. However a page option mod.SHARED.disableLanguages allow languages to be deactivated.
As such the behavior is not respected as when setting langDisable to 1 (CE are localizable with mod.SHARED.disableLanguages taken into account).
Solution: use same code as within tx_cms_layout.php.
(issue imported from #M13068)
Files
- Status changed from Accepted to Needs Feedback
- Target version deleted (
0)
- TYPO3 Version set to 4.3
The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?
I just had the same problem. I used mod.SHARED.disableLanguages = 1 and it will not be displayed when using the templavoila page module. But when using the core page module (I use both at this installation until I can drop tv) the language is still in the dropdown menu. It is in the page module and when editing the content element, in both views it should not be present.
I just checked again, it is not true, the disabled language will only be shown if there is already a translation of that language created. But there is still the problem that in the content element itself one language cannot be disabled through page tsconfig. It should be hideable completely. In my case I have default language german and a second language english (and two others), but at a special part of the page tree the default language should be english so the second english language (default lang + english lang) should not be displayed in that part of the page tree.
@Bernhard
which TYPO3 Version did you use?
@Bernhard
which TYPO3 Version did you use? As TYPO3 4.5 only gets security fixes, it should be tested with 6.1.7.
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Xavier Perseguers)
No feedback within the last 90 days => closing this ticket.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Also available in: Atom
PDF
Updated by 
Updated by