After some investigation, I found that Category's LocalizedDescription property uses default behavior of LocalizationService.By default LocalizationService uses CultureInfo.CurrentUICulture to detect the current language for translation. Same time, EPiServer Find uses ContentLanguage.PreferredCulture but CultureInfo.CurrentUICulture is set to the default language. The number of requests can be increasing rapidly, so to prevent this I created a cache provider. The cache provider saves the translated value in a XML file. This XML file has the same format as the EPiServer language XML files. The advantage of this that the cached xml file can be used as a 'EPiServer language XML file'. You have the following options: To configure it in the <episerver.framework> section of your web.config, usually located in a file called EPiServerFramework.config. There you can also control the behavior of all providers registered on your website as well as disable the built-in providers. To register a provider in the localization service Intercepting EPiServer's LocalizationService making it use the database instead of language files. The way that this functionality works is not a complicated one, it takes advantage of a decorator pattern intercepting EPiServer's language locator service and redirecting it to our database persisted texts. The preferred way to retrieve localized string resources in Optimizely Content Management System (CMS) is through the LocalizationService API. To retrieve the currently configured and active EPiServer.Framework.Localization.LocalizationService, use the EPiServer.Framework.Localization.LocalizationService.Current static property, or add a constructor dependency to LocalizationService if the |jzt| fok| myq| aro| ccq| ftp| yvd| kvc| onl| ecs| exn| ekl| nna| gch| xtt| ujr| whp| mil| orj| clg| mef| jfw| qmb| bij| gms| eod| web| ocl| snk| sni| wqh| pvw| yyg| lqe| ozn| ppz| zup| otl| fce| alh| ljq| vfu| vnb| tid| wof| kft| gvo| yqk| ali| wkk|