Overview of setting up language fallback
In XM Cloud, by default, language fallback is disabled. This topic gives you an overview of the overall process to enable it. For a detailed description of the procedures, see Enable and set up language fallback.
The following steps outline the overall process of enabling and setting up language fallback:
-
To enable language fallback functionality on all relevant sites within your environment, do one of the following:
-
Enable once in the
\App_Config\Sitecore\Services.GraphQL\Sitecore.Services.GraphQL.EdgeContent.configfile. -
Enable on each relevant site on the site definition item.
In both cases, specify whether you want to apply language fallback on an item level or a field level, or both.
-
-
If you enabled language fallback on an item level, for each relevant site, do one of the following:
-
Enable language fallback on all the items that you want to be included in the language fallback process.
-
Enable language fallback on the item templates that your site is using, for example, your page templates. Then all the pages based on the template are included in the language fallback process.
-
-
If you enabled language fallback on field level, on the relevant item templates, you need to enable language fallback on the field definition items that you want to be included in the language fallback process. You can do this for a specific language version of a field, or for all language versions of the field.
-
Define the language fallback rules for the languages that are subject to translation. You do this on the sitecore/System/Languages/[language] items. For example, you can set up a chain where, for example, English (New Zealand) falls back to English (Australian), which falls back to standard English.
-
Finally, you can fine-tune your language fallback configuration, for example, configure your search indexes to use language fallback.