.. versionchanged:: 14.0
The main module `Web` has been renamed to `Content`.
See `Feature: #107628 - Improved backend module naming and structure <https://docs.typo3.org/permalink/changelog:feature-107628-1729026000>`_
You can get a complete overview of the page tree and page translations by using the :guilabel:`Content > Info` module and choosing the :guilabel:`Localization Overview` function.
All the green entries indicate which languages the respective page is available in. The gray areas mean that no translation is available, but access to the page specifying this language is tolerated. It is also fast to create new translations from this module: use the checkboxes and hit the :guilabel:`Create new translation headers` button.
If there is no translation of a page, it will still appear by default in the website menu when this language is used. Here the home page of the Introduction Package is in German (as can be seen from the translate page title in :html:`<title>` tag), and all other (untranslated) pages still appear in the menu, albeit in the default language (English).
This behaviour can be changed. Let us edit the "Customizing" page. In the :guilabel:`Language` tab, check the :guilabel:`Hide page if no translation for current language exists`:
This is reflected in the Localization Overview:
From this it is clear that when viewing the website in German the "Customizing" page is not accessible. The menu reflects this in the frontend.
Trying to access the "Customizing" page directly with its ID will produce an error.
If you want pages only in the alternative languages you must still create a default language page in the page tree which simply acts as a placeholder. Setting this status is done by selecting the checkbox :guilabel:`Hide default translation of page`:
This is reflected in the Localization Overview:
Note
The page also appears as being unavailable in Danish, because Danish falls back to English and English is not available.
On the web site, the menu now looks like this in German:
and in English:
Trying to access the "Nur für Deutschland" page in the default language will yield an error.
Hiding pages in the default language is probably a rare thing to do, but it is possible to imagine cases where the topic of a page or section is only relevant in one of the alternative languages. Especially, if a language of the site is not only a translation but may serve subsidiaries of a company in a local context.
It is also possible to hide all untranslated pages by default with a global setting:
$GLOBALS['TYPO3_CONF_VARS']['FE']['hidePagesIfNotTranslatedByDefault'] = 1;The Localization Overview reflects this immediately:
Note how the behaviour of specific localization setting for the "Customizing" pages has been inverted. We had earlier defined the page to be hidden if no translation existed. Now it is forced to display even if no translation exists (this is reflected by its background being gray instead of red).
When editing the page properties, the label of the corresponding checkbox has changed:
Summary of colors in the Localization Overview:
- Green background
- Page is translated and viewable in this language. For translations it means that an active Alternative Page Language overlay record is present.
- Red background
- Page cannot be viewed in this language and you will see an error message if you try. Menus should automatically filter out links to pages with this translation.
- Gray background (not available for default language)
- Page will fall back to the specified fallback mode for content. It depends on the language fallback configuration set in your site configuration.












