HomeDev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunitySubmit a ticketLog In
GitHubNuGetDev CommunitySubmit a ticket

Localize the visitor group criterion

Describes how to localize your own visitor group criteria.

VisitorGroupCriterion settings localization

If you want to localize DisplayNameCategory, or Description when adding the VisitorGroupCriterion attribute, set the LanguagePath property. The property indicates a location in the language files where the Optimizely Content Management System (CMS) looks for matching keys. If you find the DisplayNameCategory, or Description keys, the user interface uses the translation.

Client-side localization

If you need a translated string on the client, you have to register the string you need in the createUI method, which can look similar to the following code:

createUI: function (namingContainerPrefix, container, settings) {
  this.languageKeys = [
    '/xml/path/to/languageKey1',
    '/xml/path/to/languageKey2'
  ];
  this.prototype.createUI.apply(this, arguments);
}

You can access the translated value by using the following syntax:

  validate: function (namingContainerPrefix, validationUtil) {
    ...
    this.translatedText['/xml/path/to/languageKey2']
    ...
  }

Enumeration localization

If you use the EnumSelectionFactory add matching keys under the enumerators part of the language files and want the names translated. For an enum called EPiServer.Sample.Criteria.Answer, the keys can look similar to the following code:

<enums>
  <episerver>
    <sample>
      <criteria>
       <answer>
         <yes>Oh yes!</yes>
         <no>No way!</no>
       </answer>
      </criteria>
    </sample>
  </episerver>
</enums>