...
Add Visitor Targets for each of the languages in the Workbench of the engine. Navigate to the Engine → Workbench → Merchandising → Visitor Targets
Select Add Visitor Target and fill up the fields. Example is shown below:
The condition option should be selected and as value on the left the “Language“ should be selected and as value on the right the language abbreviation.
A Visitor target should be added for each of the language that are selected in the backend.
Add Visibility Rules Navigate to the Engine → Workbench → Merchandising → Visibility Rules
...
Enabling the multilingual and reindexing the items, changes also the way the fields are named. Most of the fields receive a language suffix. The suffix is concatenated underscore (“_“) and the 2 letter (“en“) language abbreviation.
Example:
contenttypename → contenttypename_en
title → title_ru
Therefore, the association of fields to facets may need to be changed. If you need to visualize a facet with the content type then you will have to make as many facets as there are languages selected (and for which there are items).
Example: if English, German and Russian are selected and there are items in these languages, when indexing these articles, the document fields will receive extensions in the respective language. Thus, the article in German will not have field contenttypename, but contenttypename_de, the article in English will have contenttypename_en, and so on.
Accordingly, there is no way to have one facet associated with the content field, because in this case we will not have such a field, and three other fields with suffixes (contenttypename_en, contenttypename_de, contenttypename_en).
...
| Info |
|---|
Be aware that when the multiligual multilingual option is enabled, the association of fields to fecets facets may need to change. |
...
Queryable
One more time it is important to mantion mention that the fileds fields are changed when documents are indexed in the multilingual context. And if any of the fields, different from “content“ and “title“, are marked as queriable queryable then after indexing, this fields are changed (suffix added). So these new fields (the one with suffixed) should also be marked in the Workbench as QueriableQueryable.
...
| Info |
|---|
Content and title (with or without suffix) are automaticaty automatically marked as queriablequeryable. All other should be manually marked. |
...