Bug #78801


mod.SHARED.disableLanguages is not respected in tt_content language field

Added by Tymoteusz Motylewski over 7 years ago. Updated over 4 years ago.

Should have
Backend User Interface
Target version:
Start date:
Due date:
% Done:


Estimated time:
TYPO3 Version:
PHP Version:
Is Regression:
Sprint Focus:


In TYPO3 8:
steps to reproduce
1. set mod.SHARED.disableLanguages
2. edit tt_content
3. see the list of available languages not being filtered in the tt_content "language" select

This feature was implemented originally in
and is documented in

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Feature #20014: Page TS option to disable available languagesClosed2009-02-13

Actions #1

Updated by Tymoteusz Motylewski over 7 years ago

  • Category set to Backend User Interface
Actions #2

Updated by Silvia Bigler over 7 years ago

We have the same issue on a TYPO3 7.6.15.

It occurs not on only on tt_content, but also on sys_categories, pages_language_overlay and others.
Additionally, pages_language_overlay does not respect if a sys_language is set to hidden.

Actions #3

Updated by Lidia Demin over 6 years ago

I can confirm this for TYPO3 7.6.23. Can someone give a hint, what the origin of this issue can be?

Actions #4

Updated by Christian Hackl over 6 years ago

it seem i have the same issue here - TYPO3 8.7.10

Actions #5

Updated by Lidia Demin over 5 years ago

Still having this problem in TYPO3 8.7.24. Has someone an idea?

Actions #6

Updated by Riccardo De Contardi about 5 years ago

I tested this TS property on 6.2.31, 7.6.32, 8.7.26, 9.5.7 and 10.0.0-dev (latest master); and so far I've seen that

- it seems to affect only the "make new translation of this page" link in page module > languages view
- It works only on 7.6.32 and 8.7.26 (and only for the link I mentioned)

I don't know if it has ever meant to work as described on this issue; the documentation just says:

Comma-separated list of language UID which will be disabled in the given page tree.

Actions #7

Updated by Benni Mack over 4 years ago

  • Status changed from New to Closed

Hey Tymek,

I will close this issue now. It's a matter of a very bad conceptual problem which we overcame with Site Languages where you can do this on a per-tree level, and also on a per user and per-workspace level, if necessary.

This option now works for all areas (page module, form engine etc).

Hope it's oK with you, but it's hard to fix in TYPO3 v8, and putting the energy in there does not seem reasonable.


Also available in: Atom PDF