The Site Management > Sites module lets you specify which languages are active for your site, which languages are available, and how they should behave. New languages for a site can also be configured in this module.
When the backend shows the list of available languages, the list of languages is limited to the languages defined by the sites module. For instance, the languages are used in the page module language selector, when editing records or in the list module.
The language management provides the ability to hide a language on the frontend while allowing it on the backend. This enables editors to start translating pages without them being directly live.
In case no site configuration has been created for a tree, all configured
languages are displayed. In this case the page TSconfig options
mod.SHARED.disableLanguages settings are also considered -
those are obsolete, if a site configuration exists.
Language fallbacks can be configured for any language except the default one. A language fallback means that if content is not available in the current language, the content is displayed in the fallback language. This may include multiple fallback levels - for example, "Modern Chinese" might fall back to "Chinese (Traditional)", which in turn may fallback to "English". All languages can be configured separately, so you can specify different fallback chains and behaviors for each language.
Example of a language configuration (excerpt):
languages: - languageId: 0 title: English navigationTitle: '' base: / locale: en_GB.UTF-8 flag: gb
Defines, if the language is visible on the frontend. Editors in the TYPO3 backend will still be able to translate content for the language.
For the default/main language of the given site, use value
0. For additional languages use a number greater than
0. Every site should have at last one language configured - with
Once pages, content or records are created in a specific language, the
languageIdmust not be changed anymore.
The internal human-readable name for this language.
My custom very British title
Overrides the global website title for this language.
Optional navigation title which is used in
HMENU.special = language.
string / URL
The language base accepts either a URL or a path segment like
Allows different base URLs for the same language. They follow the same syntax as the base variants on the root level of the site config and they get active, if the condition matches.
baseVariants: - base: 'https://example.localhost/' condition: 'applicationContext == "Development"' - base: 'https://staging.example.com/' condition: 'applicationContext == "Production/Sydney"' - base: 'https://testing.example.com/' condition: 'applicationContext == "Testing/Paris"'
string / locale
The locale to use for this language. For example, it is used during frontend rendering. That locale needs to be installed on the server. In a Linux environment, you can see installed locales with
locale -a. Multiple fallback locales can be set as a comma-separated list. TYPO3 will then iterate through the locales from left to right until it finds a locale that is installed on the server.
Changed in version 12.4: The information is now automatically derived from the locale setting.
Use this property to override the automatic hreflang tag value for this language.
You have "German (Germany)" (which is using
de-DEas locale) and "German (Austria)" (which is using
de-ATas locale). Here you want to set
deas generic fallback in the
de-DElocale when using hreflang tags.
You want to explicitly set
x-defaultfor a specific language, which is clearly not a valid language key.
Deprecated since version 12.3: It is not needed to set this property anymore, and is removed from the backend UI. The information is now automatically derived from the locale setting. Using this property will trigger a PHP deprecation notice.
Language identifier to use in TYPO3 XLIFF files.
The flag identifier. For example, the flag is displayed in the backend page module.
The language fallback mode, one of:
Fall back to another language, if the record does not exist in the requested language. Do overlays and keep the ones that are not translated.
It behaves like the old
config.sys_language_overlay = 1. Keep the ones that are only available in default language.
fallbackbut removes the records that are not translated.
If there is no overlay, do not render the default language records, it behaves like the old
hideNonTranslated, and include records without default translation.
Fall back to another language, if the record does not exist in the requested language. But always fetch only records of this specific (available) language.
It behaves like old
config.sys_language_overlay = 0.
comma-separated list of language IDs
The list of fallback languages. If none has a matching translation, a "pageNotFound" is thrown.