Fixed issues in Content Delivery 11.0.0
With the release of Content Delivery 11.0.0, with which the product is compatible as of SDL Tridion Docs 13 SP2, a number of Content Delivery issues were fixed.
| ID | Description |
|---|---|
| CRQ-6874 | Because authorization was not supported, you had to disable the X-Pack Plugin in your Elasticsearch environment. This is now fixed. |
| CRQ-5822 | It was possible to retrieve search results and page content non-securely from an OAuth-secured IQ Query Service. You now need authentication. |
| CRQ-5853 | If you remove a topic and then republish the publication, the sitemap.xml would still contain the topic. This was resolved. |
| CRQ-5858 | If you remove a topic and then republish the publication, you could still access the topic through its specific URL and as a search result. This is no longer the case. |
| CRQ-5844 | If the content was published with multiple condition values available (that is, if the content is made personalizable by the visitor), the visitor could not successfully personalize the output using a condition containing non-Latin characters (like, say, Hebrew characters). This is resolved |
| CRQ-5788 | An <area> DITA element, representing an area inside an image map, rendered as an HTML <a> element when it should be an HTML <area> element. This is now resolved. |
| CRQ-3581 | Unlike standard storage configuration in the Storage Layer configuration file, cd_storage_conf.xml, State Store storage configuration in the Content Deployer configuration file, deployer-conf.xml, only allowed you to configure connecting with SID. It did not enable you to set a ServiceName property, but it does now. |
| CRQ-3116 | The Unix version of the express installation script quickinstall.sh did not accept the --all switch. It does now. |