23-07-2018

List of significant changes between version 11 and 12

  • The mechanism for bootstrapping configuration and content into the repository has been replaced. Preparing for the upgrade to Hippo 12 includes getting familiar with the new mechanism and its main concepts. Using the new mechanism comes with a number of changes to the structure of the repository data. 
  • Some builtin or standard Repository nodetypes have been changed.
  • HST's channel-related configuration has been restructured to be less complex.
  • HST Configuration Editor has been removed from Hippo CMS.
  • Several 3rd party dependencies have been updated compared to Hippo CMS 11 (hippo-cms7-project: 28.x to 29.y):
    • Most notably, Hippo CMS 12 uses log4j2 rather than log4j
    • On top of supporting Tomcat version 8.0, CMS 12 also supports Tomcat 8.5
    • Wicket has been upgraded to 6.26.0
    • HtmlCleaner has been upgraded from version 2.12 to 2.21

      There is a breaking change in TagNode#addAttribute method which does not override existing attributes anymore. If your project is using this method, and intends to override existing attributes, the TagNode#removeAttribute method should be used before TagNode#addAttribute.
    • CXF has been upgraded from from version 3.1.6 to 3.1.13

    • Jackson2 has been upgraded from version 2.4.5 to version 2.8.8

    • Groovy has been upgraded from version 2.4.7 to 2.4.11

  • The Elasticsearch Webapp (hippo-addon-targeting-demo-support-elasticsearch) used for local development is no longer suppported. As alternative you can use the Elasticsearch Maven Plugin for local developement.
  • The system requirements page has been updated with the latest system and infrastructure requirements.

Bloomreach Experience Manager changes

  • For the Relevance Module, Elasticsearch 2.x is no longer supported. Upgrade to Elasticsearch 5.5 or 5.6 is required.
  • A Google API key is now required to enable to map widget on the Realtime map of the Audiences perspective added by the Relevance Module. See Add the Relevance Module to a Project, section "Configure Google API Key".

 

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?

    We rely on cookies

    to optimize our communication and to enhance your customer experience. By clicking on the Accept and Close button, you agree to the collection of cookies. You can also adjust your preferences by clicking on Manage Preferences. For more information please see our Privacy policy.

    Manage cookies
    Accept & close

    Cookies preferences

    Accept & close
    Back