Fallback languages

For many multi-language websites, only parts of the website content exist in all available languages. The reason can be that translations are not yet ready, content is not relevant for a specific language, or that some content should always display in a defined language.

You have the following options:

  • Unless a fallback or replacement language is defined, content is invisible to visitors browsing the website in a language into which content has not been translated.
  • Define a fallback language, in which the content is displayed until the content is available in the desired language.
  • Define a replacement language, in which content is always displayed regardless of the language in which the content exists. If a replacement language is defined for some content, a fallback language does not apply.

Fallback and replacement languages may cause mixed languages to be displayed on the website.

Setting fallback and replacement languages

Fallback and replacement languages are defined from the All Properties edit view, when editing a page or a block and then selecting Tools and Language Settings.

Language settings are inherited from the parent page. If you are redefining language settings for a subpage to a parent page with language settings defined, you need to deselect Inherit settings from the parent page “xxx” in the Language Settings dialog, to define settings for the subsection.

See also

  • Refer to Translating content for information on how to translate CMS content into different languages.
  • Refer to the Languages add-on for more information on how to extend the functionality in Episerver for translating content into multiple languages.
back to top




Episerver User Guide update 16-2 | Released: 2016-03-31 | © Episerver 2016 | Send feedback to us