Text, Site Admin, Manage Site, Multilingual sites

There are three levels of languages you can enable by default in Salesforce: fully supported, end user, and platform-only languages.

Once these are enabled in Salesforce, they become available in OrchestraCMS.

• As administrator, you can add up to 20 languages to OrchestraCMS.
• The OrchestraCMS Multilingual Sites feature requires a Multilingual Sites license.
• The list of languages that are available to add to your site is based on your Salesforce language settings.

Enable end user or platform-only languages in Salesforce

1. In Salesforce Setup, expand Company Profile, and then click Language Settings.
2. On the Language Settings page, do one or both of the following:
3. Select the Enable End User Languages check box.
4. Select the Enable Platform Only Languages check box.
5. Click Save.

Set the default language for your site

When you install a site or upgrade OrchestraCMS from a non-multilingual version, you are required to set a default language. This is the language that will be displayed on your site’s pages and content for editing and translating. It is also your site’s fall-back language, if you choose that option.

Install the OrchestraCMS Multilingual Sites license

Your OrchestraCMS application periodically checks for changes to your OrchestraCMS licenses. If you have purchased the OrchestraCMS Multilingual Sites license and do not see it listed on the Manage Licenses page in OrchestraCMS Setup, you can manually check for updates.

Manually check for license updates

1. In OrchestraCMS Setup, under Site, click Licenses.
2. On the Licenses page, click Check Now.

The OrchestraCMS Multilingual Sites license appears in the Feature Licenses list when your license has been processed and synced with your organization.

• When the OrchestraCMS Multilingual Sites license is enabled, the Languages and Translation Groups menu items appear on the OrchestraCMS Setup sidebar.

Add, edit, and disable languages

• The list of languages available for your organization to use in OrchestraCMS always includes the default language, which you set during the installation or upgrade process for OrchestraCMS.
• Once you add a language to OrchestraCMS, it can be used to create and translate content and pages.

Add a language to OrchestraCMS

1. In OrchestraCMS Setup, click Languages.
2. On the Manage Languages page, click Add.
   
3. In the Add Language dialog, set the following properties:
   • Name (required). The name of the language as it will appear in the OrchestraCMS interface.
   • Select Language (required). The language you are adding from the list of enabled languages in Salesforce.
   • Description (optional). A description for the language (only displayed on the Manage Languages page). Most of the time, you will not need to add a description, as it is self-evident; however, you might want to use the description field to indicate to your translators you'd like special treatment of the language — a dialect, perhaps.
   • Set Language Priority (optional). A whole number, 1 or above, that determines the order that languages are displayed in picklists in OrchestraCMS. The default language is assigned a value of 0 and always displays at the top of lists. If two or more languages are assigned the same priority number, they will be listed in alphabetical order at that location in the list. For example, if two languages are assigned a priority of 2, they will appear in alphabetical order after the default language and any languages assigned a priority of 1. Languages that do not have a priority number are listed in alphabetical order after the default language and any other languages that have a priority number assigned.
   • Fall back to [your default language]. Determines whether a site visitor will see content items or pages in the default language (if available) if the visitor is attempting to view the site in another language but there is no translation available for the content item or page currently being viewed.
4. Click Save.

You can edit a language after it is created. With the exception of the default language,  you can also modify all properties of a language. (For the default language, you can only modify the Name and Description fields.)

Edit a language

1. In OrchestraCMS Setup, under Site, click Languages.
2. On the Manage Languages page, select the check box next to the language you want to edit.
3. Click Edit.
4. In the Edit Language dialog, modify language properties as required, and then click Save.

You can disable a language to make it no longer available to assign to new content items. However, disabling a language doesn’t change any published pages or content items that were created in, or translated to, that language.

• A disabled language can be enabled again by selecting it and clicking Enable.

Disable a language

1. In OrchestraCMS Setup, under Site, click Languages.
2. On the Manage Languages page, select the check box next to the language you want to disable.
3. Click Disable.

Change the default language

There might be a situation when you want to change the default language.

For example, if your primary business location moves to a region with a different official language, you can change the default language in OrchestraCMS Setup. (The new default language must be added to OrchestraCMS before it can be designated as the default).

When the default language is changed, the previous default language and the new default language swap priority designations.

1. In OrchestraCMS Setup, under Site, click Languages.
2. On the Manage Languages page, select the check box beside the language that you want to make the default language.
3. Click Set Default.
   

Control the site’s display language

1. There are a variety of methods for displaying your site language for specific users. As a first method, you can utilize the Language Field in Salesforce user records. This method is only available to users who are signed in to a secure site (i.e., a portal, community, or intranet site).
2. The display language for a specific user is determined using the following logic:
   • If the Always use Salesforce User Language to determine language check box is selected,
   • and the current user is signed into the site,
   • and the Language field on the visitor’s user record with one of the languages is associated with the site,
   • then the site is displayed in that language.
   • Otherwise, if a language parameter has been passed to the URL (e.g., via a language selection picklist), and that language is one of the languages associated with the site, then the site is displayed in that language.
   • Otherwise, if there is a cookie that has stored the site visitor’s language from a previous session, and that language is one of the languages associated with the site, then the site is displayed in that language, provided Enable Language Cookie for this site is enabled.
   • Otherwise, the preferred languages that have been set in the visitor’s browser are examined in order of priority, and if one matches a language associated with the site, then the site is displayed in that language.
   • Otherwise, if a language has not yet been determined, the site is displayed in the site’s default language if the “Fall back to default language” check box has been cleared.

The Language Fallback Option

If a piece of content does not have the user’s language translated, you can select the option to fall back to your default language. For instance, a page might have content translated in both English and French, with English as the default language. A piece of content might be created in the default language (in this case, English), and placed on the page. If the content has not been translated into French, but it is viewed by a French user, the displayed content will fall back to the default language (in this case, English).

Set the Language Fallback Option

1. In OrchestraCMS Setup, select Languages.
2. In  Manage Languages, click the Add button.
3. In Add Language, if you would like the content to remain blank rather than fall back to the default language, clear the check box labelled Fall back to [your default language].
   

Language Selector

You can add the Language Selector content template to your pages so your site visitors can view the page in another language. Public site visitors can select any language the current page supports. Authenticated users (Intranet or Communities) will see multilingual pages in the language specified on their user record unless you disable the “Always use Salesforce User Language to determine language” option shown in Setup under Manage Languages.

To use the Language Selector content template

1. In Create New Content dialog:
   • In Select Content Type, select the Utility content type.
   • In Select Content Template, select the Language Selector content template.
2. In the Language Selector Label, enter the text you want.
3. In the Actions panel, click Save.

We recommend that you translate the Language Selector Label into all the languages the site supports.

When you drop the Language Selector on a page, it displays a list of languages the page has. When you drop the Language Selector on a master page to make it available to all pages using that master page, it will always display the list of available languages in the master page.

Pages which include only a subset of the available languages in the master page will not display if a language that is available only in the master page was selected. We recommend that you consider your site page configuration before deciding how best to implement the Language Selector.

To enable the Language Selector for authenticated users

1. In OrchestraCMS Setup, under Site, click Languages.
2. On the Manage Languages page, clear the Always use Salesforce User Language to determine language check box.
3. Also under Manage Languages, there is a Site Language cookie option: Enable language cookie for this site, which is selected by default.
   

Enabling the language cookie for an OrchestraCMS site allows the following actions:

1. Once the language selector content is placed on a page, that page can then be viewed in one of the available languages, because an ocmsLang cookie is generated containing the selected language code.  
2. When determining the language in which to display a page, OrchestraCMS will look at the ocmsLang cookie to determine the language if other conditions are not met.

Manage administrative permissions for the OrchestraCMS Multilingual Sites feature

The default OrchestraCMS System Administrator profile is automatically and permanently assigned the following permissions unless the OrchestraCMS Multilingual Sites license expires:

• Manage Languages. Provides access to the Languages menu item in OrchestraCMS Setup and all of the related features on the Manage Languages page.

• Manage Translation Groups. Provides access to the Translation Groups menu item in OrchestraCMS Setup and all of the related features on the Manage Translation Groups page.

The system administrator can also assign these permissions to the site administrator profile.

Manage languages permissions for a profile (for the site administrator only)

1. In OrchestraCMS Setup, under Site, click Profiles.
2. Click Edit next to the profile that you want to modify.
3. Under Administrative Permissions, enable or disable the Manage Languages and Manage Translation Groups permissions as required.
4. Click Save.

Build a custom content editor for a multilingual site

Custom content templates, developed specifically for your organization, are also compatible with the multilingual feature. In some cases, it can be beneficial to have a developer make content template adjustments to custom content editors, because this makes it easier for translators to use.

The Split View feature, which allows translators to view two language instances of a content item in the content editor, is easiest to use if the following best practices are used to develop custom content editors:

• The content editor should be 625px wide or less.
• All input fields should stack on top of each other.
• Field labels should appear above the fields.

Manage translation permissions and groups

There are two items that determine whether an OrchestraCMS user has permission to translate a content item to a specific language: OrchestraCMS profile permissions and translation group membership.

• OrchestraCMS profile permissions determine whether a user is able to translate a content item of a specific type (e.g., Text, Media).
• Translation group membership determines which languages a specific user is able to translate.
  • When a language is added to a site, a translation group for the language is automatically created. OrchestraCMS users with “Manage Translation Groups” permission have the ability to add and remove users from translation groups.

If you have a multilingual licence installed, even if you are only using the single default language, users other than the system administrator need to be added to the default language translation group before they can create or edit content and pages. If you don’t have the multilingual licence installed, the translation groups are not present in OrchestraCMS Setup.

Profile translation permissions determine what OrchestraCMS users can do with content based on Content Type.

For each Content Type, you can set permission to Create, Edit or Publish content. With multilingual, there is a fourth permission: Translate.

The Translate permission allows specific users with that permission to translate existing content. Editors can create and build content in one language; translators can translate that content without being able to change the content or structure.  

Provide content translation permissions to an OrchestraCMS user profile

1. In OrchestraCMS Setup, under Site, click Profiles.
2. Next to the profile that requires translation permissions, click Edit.
3. In the Content Permissions area, click to select the Translate box next to the content types that you want that profile to be able to translate.
4. Click Save.

Add or remove translation group members

1. In OrchestraCMS Setup, under Site, click Translation Groups.
2. On the Manage Translation Groups page, in the row of the translation group where you want to add or remove members, click Edit.
3. In the Manage Group Members dialog, do one or both of the following:
4. From the Available Users list, click to select one or more users to add to the translation group, and then click Add.
5. From the list of members included in the translation group, click to select one or more to remove from the translation group, and then click Remove.
6. Click OK.

Manage multilingual content

Creating a multilingual content item is similar to creating a standard content item, except that at least one language must be selected when the content is created. The languages you can select are based on the languages that have been added in OrchestraCMS Setup.

Assign languages to content

When you create a new content item with the OrchestraCMS Multilingual Sites license activated, you must select at least one language for the content item in the Create New Content Wizard. The default language is automatically selected, but you can remove this language if you have chosen at least one other language.

After the content item is created, you can modify the languages through the content item’s properties, either from the quick access properties panel or by viewing all properties.

Change the languages of a content item

1. Open the content item in the content editor.
2. In the Actions sidebar, click Properties.
3. In the Languages area, select or clear the check boxes next to languages that you want to add or remove. (At least one language must be selected.)
4. Click Save.

If you clone a multilingual content item, all the languages and translations are copied to the new content item.

Translate a multilingual content item

The translation procedure for all content items is, in general, the same. The Split View feature in the content editor allows you to view the content item in two languages at the same time.

OrchestraCMS users who have editing permissions for the content type can modify fields that are not translatable while they are working in any language, but any changes made are reflected across all languages.

To translate a content item

1. Open the content item in the content editor.
2. In the Actions sidebar, click Split View.
3. Using the language picklists on each side of the split view, select the language you are translating from and the language you are translating to.
4. On the side of the split view that contains the language you are translating to, edit all applicable fields to translate them to the appropriate language.
5. When translation is complete, select Translated from the translation status picklist.
6. In the Actions sidebar, click Save.

You do not have to translate all fields during the same session. You can save the content item, return later, and mark it as translated when you are finished.

By default, the highest priority language displays on the left side of the split view, and the next highest priority language displays on the right side of the split view.

Under the language selection list, your status is displayed.

• “Currently Viewing” means you have read-only status because the content is being edited by someone else or you are not a member of that language translation group.
•  “Currently Editing” means you now have editing status, and the content is currently locked to other users (by you).

Some fields are not translatable and remain the same across languages. The following types of fields are not translatable:

• Check boxes
• Radio buttons
• Fields relating to the structure of the content (e.g., height, width, positioning)
• Links to pages (the appropriate language will be automatically selected for pages on your site)

The following content types have some additional considerations for translation:

• Menu
• Taxonomy
• Form

Translate a Menu content item

OrchestraCMS users who have translate permissions for a menu content item can translate the following items:

• Labels
• Sublabels
• External page links (if applicable)
• Media library file links (if applicable)
• OrchestraCMS page links

If the menu item links to an OrchestraCMS page, the language of the page is automatically selected and can’t be changed by a translator. However, the page, properties, and URLs available for each language can be translated separately. Translators can’t alter the structure of the menu or other menu fields.                                                                                                                                  

Translate a Taxonomy content item

When you create a multilingual taxonomy content item, the category labels must be translated for the various languages assigned to the taxonomy. This can be done in the Taxonomy Menu content template.

The structure of the taxonomy must be the same across languages. If an OrchestraCMS user has edit permissions, and they modify the structure of the taxonomy in any language, the change is reflected across all languages.

Translate all child category labels at the same time

1. In Create New Content, check the boxes beside your required language(s).
2. Click Finish and Edit.

Once you have created your taxonomy, in Taxonomy Menu, click on the menu icon to the right of the top category. In the drop-down panel, click Translate Children.

Translate a single category label

1. In the category panel, click on the menu icon to the right of the category.
2. In the drop-down panel, click Translate Category.

Include alternate Taxonomy loader

You can create a taxonomy that appears in different languages by choosing the languages from a picklist for translation.

Translate a Form content item

When you create a multilingual form content item, any text and button labels included in the form should be translated for the various languages assigned to the content item.

The structure of the form must be the same across languages. If an OrchestraCMS user has edit permissions, and they modify the structure of the form in any language, the change is reflected across all languages.

• If you have editing permission to a language and you also belong to the translation group for that language, you can edit the structure of the form.

• In the Properties panel, you can choose targets for the form.

• Any structure changes that occur in one language are applied to all other languages for the form content item.

Create a multilingual OrchestraCMS site map

When you add a page that has been translated into different languages to your site map, you can view it in the site map depending on the language you want by using a language selector shown at the top of the site map tree.

Switching between languages displays page names in the language you have selected. Nameless placeholders will appear for pages that do not have a name specified in the language currently being used to display the site map. These are required to maintain the structure of the site map.

Manage multilingual pages

Creating a multilingual page is similar to creating a standard page, except that you must select at least one language when you create the page. The languages you can select are based on the languages that have been added in OrchestraCMS Setup.

Assign languages to pages

When you create a new page with the OrchestraCMS Multilingual Sites license activated, you must select at least one language for the page in the Create New Page dialog. The default language is automatically selected, but you can remove this language if you select at least one other language. You can select as many languages as required for the page.

After the page is created, you can modify the languages from the page properties.

Change the languages on a page

1. Open the page in the page editor.
2. In the Actions sidebar, click Properties.
3. In the Languages area, select or clear the check boxes next to languages that you want to add or remove—you will need to choose at least one language.
4. Click Save.

If you clone a multilingual page, all the languages and translations are copied to the new page.

Assign a master page to a multilingual page

Multilingual pages can be built on master pages provided the master page has the same language as the new page. The master page can have additional languages, but not fewer than the page to which it is being applied.

Languages are applied to master pages in the same way they are applied to standard pages.

You can assign a master page from the Create New Page dialog when you first create a page or from the page editor after you have finished creating the page.

Master pages that are not associated with all the languages applied to the page are not available to select.

If you want to add a language to a page that already has a master page assigned, but that language is not associated with the master page, you must either remove the master page or add the language to the master page, and then publish it before you can add the language to the page.

Translate page properties

You can translate the properties of a page using the quick access properties panel.

1. Open the page.
2. In the Actions sidebar, click Properties.
3. In the Properties panel, click Translate Properties.
4. In the Translate Properties dialog, translate the page name and URL.
5. Publish the page before adding it to your site map.
6. Click OK.

Manage a translation approval process

You can configure an approval process in Salesforce before you place final translated content on your live site.