Multilingual Features
| Category | Notes |
|---|---|
| Module Location | Feature.Language |
| Recommended | If Needed |
| Default | On |
| Dependencies | None |
| Pipelines Targeted | HttpBeginRequest |
| Events Targeted | None |
| Site Settings | /sitecore/templates/SF/Feature/Language/Interface Templates/_SiteLanguageSettings |
| Page Settings | None |
| Patch Config | Feature.Language\Language.config |
| Other | Sample Custom Fallback Item Provider with disabled config’s included for example fallback strategies. |
This feature handles two use cases: Fallback Language and Language Enforcement.
The Fallback Language feature was implemented before Sitecore natively supported it and it still remains because the default Sitecore implementation is a global implementation in that you can define one language will fallback to another language. The ASF implementation enables the default language to be defined at the Site Level in the Site Configuration file. So each site can have a base language, making the fallback process more efficient. Simply add the "FallbackLanguage" attribute to the site configuration and it will work properly.
Another additional strategy sample is provided. This strategy will always fallback to a default language (configured in Sitecore Setting) and then defer to any other version if it exists.
Language enforcement addresses a different issue. Out of the box, Sitecore will try to resolve valid two letter local codes when requested which could cause errors if they are not setup. Instead ASF allows you to define valid languages at the site level and will ensure proper 404 errors are returned if a visitor requests a page in a language that is unsupported.
