Known issues in Experience Optimization
This section describes the known issues in Experience Optimization.
- Promotions cannot find Components that are published before indexing
-
Problem: If you publish Components before creating your Elasticsearch indexes, Promotions will not be able to find these Components, even if you republish the Components.
Even if you then run the scripts to create indexes and republish the Components, they will still not be found if a Promotion is triggered and you will see in the log:
18-11-14 08:56:02,508 DEBUG [http-nio2-8094-exec-9] ElasticSearchXoQueryProvider - Listing documents on xo-contentfragments/contentfragments via content-fragment 2018-11-14 08:56:02,512 DEBUG [http-nio2-8094-exec-9] ElasticSearchXoQueryProvider - Query matched 8 item(s) in the system. 2018-11-14 08:56:02,512 DEBUG [http-nio2-8094-exec-9] DefaultResultHandler - Setting context Publication to 11 2018-11-14 08:56:02,512 DEBUG [http-nio2-8094-exec-9] DefaultResultHandler - Filtering out Promotion 'My Promotion', as it does not contain any items.Workaround: You must start over with a fresh index and then publish again. Wipe existing Elasticsearch indexes, run the scripts to recreate the indexes, and publish the Components.
- Error when Elasticsearch query results contain more than 10,000 items
-
Problem: If you perform a query against Elasticsearch and the results exceed 10,000 total promotions or content fragments (items), the Experience Optimization Management Service or Query Service produces an error.
Workaround: Such large results are not expected under normal Experience Optimization usage since more than 10,000 items on a webpage is not typically desired. If you need to display more than 10,000 results, increase the value of the index.max_result_window index setting in the Elasticsearch configuration from the default 10,000 items. For details, refer to the Elasticsearch documentation. - Error when creating a new Promotion with a SDL Tridion Sites 9 version of Content Manager and an 8.5 or 8.1.1 version of the Experience Optimization Management Service
-
Problem: If you try to create a new Promotion from the SDL Tridion Sites 9 version of Content Manager with Experience Optimization, but are running an older 8.5 or 8.1.1 version of Content Delivery with the older Experience Optimization Management Service, you receive an error. You can, however, save the Promotion.
- Localizing Schema field descriptions in a child Publication changes the Attribute display name
-
Problem: When you do content filtering in a Promotion, and when you examine Attributes based on SDL Tridion Sites Schema fields in Elasticsearch, the Attribute display name shows the Schema field description as it is in the specific Publication from which you published the Component last. Typically, this is not a problem, as Schema field descriptions are inherited unchanged down the BluePrint hierarchy. But if someone localizes the Schema field description in a child Publication, the Attribute display name shows the localized Schema field description or the original one, depending on which Publication you last published from.
-
Cannot use
tcdl:Linkin combination with Experience Optimization placeholders -
Problem: You cannot use the
tcdl:Linktag in combination with Experience Optimization placeholders because the Content Delivery TCDL handler tries to validate these URIs when publishing and throws exceptions when it encounters invalid URIs. For example, the following code will fail to publish:<tcdl:itemContent maxItems="10" var="searchResult"> <tcdl:itemContentTemplate> <p><tcdl:Link type='Component' origin='@@Page.Id@@' destination='##componentUri##' templateURI='tcm:0-0-0' linkText='Read more...' textOnFail='false' linkAttributes='' /> </p> </tcdl:itemContentTemplate> </tcdl:itemContent>Solution: To solve this problem, use the
tridion:ComponentLinkortcdl:ComponentPresentationtags because these URIs are validated at runtime.