Known issues
This section describes the known issues in Experience Optimization.
- Management service requires correctly configured connection to Content Data Store but does not use it
-
Problem: Even though the Experience Optimization Management service does not interact with the SDL Web Content Data Store at all, the service will only work if you configure the Content Data Store database details in the Storage Layer configuration file, cd_storage_conf.xml, of the service.
Solution: When you set up the Management service, in its cd_storage_conf.xml, configure the details of the Content Data Store.
- Slow performance in Internet Explorer
-
Problem: When you open multiple tabs in Internet Explorer, the performance of the GUI drops.
- REL support for Page View
-
Problem: The
<tcdl:query>tag attributeviewis not supported for REL implementations. Theviewattribute triggers promotions depending on the type of Web page a user is viewing. - 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 Web Schema fields in Fredhopper, 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.