7.8.1 release notes - BloomReach Experience - Open Source CMS

7.8.1 release notes

February 28, 2013

Hello everyone,

I am happy to announce the General Availability of Hippo CMS 7.8.1, the first update in the 7.8 series for both the Community and Enterprise Edition. This update concentrates on quality and stability of CMS 7.8 and marks the rollout of new add-ons to improve the Hippo experience for all audiences: developers, editors and marketers.

I have summarized the availability and improvements for you below to give you a more detailed view of what this update contains. Don’t hesitate to get in touch with me if you have any questions.

I wish you all great success in creating those digital miracles!

Oscar Scholten - Product Manager


All functionality described in this announcement is available in the Hippo Community Edition, with the exception of the Relevance Module (Targeting add-on) and the Advanced Search and Bulk Operations add-on which are available as part of the Hippo Enterprise Edition only.

This release marks the General Availability (GA) for Enterprise Edition and Limited Availability (LA) for the Enterprise Relevance Module. New implementations that do not utilize relevance capabilities can be executed by all Customers and Hippo Certified Partners. Projects not using the Relevance Module can go live using 7.8.1. A selected group of partners will be able to implement and launch projects that make use of targeting functionality together with Hippo support. If you are interested in this, please contact your account manager for the relevant contacts.

In May 2013 we expect to release General Availability for the Enterprise Edition including the Relevance Module and Upgrade Pack for CMS 7.7 installations. This is when all aspects of the Hippo Enterprise Edition and the Relevance Module are generally available for implementation by Hippo Customers and Hippo Certified Partners. Customers upgrading from CMS 7.7 are advised to wait until May 2013 in order to benefit from the Upgrade Pack.

The LA and GA releases are and will be fully backward compatible with the FCS released in December last year.

Deprecation Notice

In Hippo CMS 7.6 we introduced relaxed node types to simplify the creation and maintenance of document types. Currently, Hippo supports both the use of strict, as well as relaxed node types. In the coming year, we expect to work on several improvements that allow us to introduce a more user friendly and efficient way of enforcing the structure of your content types. From this release onward, the use of strict node types for content documents has been deprecated and we highly recommend new projects not to rely on this mechanism.

Hippo CMS 7.8.1 and all future maintenance updates for 7.8 are now certified to work with either Java 6 or Java 7. We expect that the next release after 7.8 will only support Java 7.

New Functionality

Advanced Search and Bulk Operations Add-On

Advanced Search and Bulk Operations, enabling CMS users to better manage their content through the combination of powerful search functions and the capability to perform bulk workflow on selections within the search result. For example, CMS users can now search for all unpublished documents in the CMS, select a subset from the list of results and publish them through one bulk operation.

The module provides the capability to search using standard document properties including document type, publication status, last editing author, document location and creation, last modification and publication date. This list can be extended with filters on project specific document type fields, allowing CMS users to filter for instance on taxonomy labels that have been applied to a document.

Developers can additionally extend available bulk operations beyond the default publishing functionality.

The Enterprise Documentation for developers describes how to include the module and customize it for your project.

Misc Improvements

Several smaller improvements have been implemented in this release, presented below broken down by target audience.

CMS users, marketers, editors and authors:

  • The CMS UI is now also available in French and German, next to Dutch and English that shipped with 7.8.0.
  • Sharing documents between colleagues has been simplified. When editing documents in the CMS, the browser URL bar is automatically updated to contain a link that can be shared with co-workers through email or instant messaging. Once your co-worker opens the link, he will be asked to log into the CMS, and then the CMS will open with the document immediately visible.
  • Projects that are already working with the Relevance Module can now configure which user agents should be suppressed in the Real Time Visitor Analysis screen, for instance search engine spiders.
  • Documents open faster thanks to several small performance improvements such as lazy loading for the translation, view and share menus.


  • Hippo CMS 7.8 is now certified to work with either Java 6 or Java 7. Note that compiling Hippo from scratch needs to be performed against the Java 1.6 target due to a dependency in our stack.
  • The eventing mechanism has been extended to provide with each event an additional hipposys:interaction property that allows developers to discern for instance whether a depublication event was triggered either as a stand-alone event, or as one of the workflow steps for a document copy.
  • The Repository API module has been extended to expose a scheduling service that can be used to schedule jobs with the repository.
  • In 7.8.0 we introduced a new tool in the console for creating and applying JCR patches. In this release we have further simplified the syntax of the patch format, making it easier to manually inspect and edit the patches.
  • The HST supports dynamic Java resource bundles management in the Repository and seamless integration with JSTL tag libraries. In order to provide a more flexible and convenient way than the current default practice dealing with localization issues, HST provides a nicer option to manage resource bundles in the Repository and to configure the default resource bundle per virtual host group, virtual host, mount or sitemap item level, supporting the standard JSTL tag libraries seamlessly.
  • As part of the work on Advanced Search, we introduced a faster mechanism for performing range queries on date properties that can be used from the HST as well.

System Administrators:

  • The standalone repository consistency checker can now perform fixes against a running clustered repository.
  • Hippo Repository uses Lucene to index the data contained in the repository for fast querying. Under certain circumstances (for instance incorrect shutdown) the Lucene index and the repository content could get out of sync. A new, faster mechanism is available to check and fix these inconsistencies.
  • The HST can be configured to more efficiently load updates in the HST configuration model. This will help prevent web site visitors to experience hiccups when reloading large configurations in busy environments.

New Project

To try out the new functionality of Hippo CMS 7.8 using the maven archetype see instructions on the Hippo Trail.

You can also check out and run the Hippo Go Green demo:

  • svn co http://svn.onehippo.org/repos/hippo/hippo-demos/hippo-go-green/tags/hippogogreen-3.07.02
  • cd hippogogreen-3.07.02
  • mvn install
  • mvn -P cargo.run
  • open the cms and site in a browser at http://localhost:8080/cms and http://localhost:8080/site, respectively

Hippo Certified Stack

Hippo CMS 7.8 works with Java 6 and 7 and Apache Tomcat 6 and 7. As part of our Enterprise Edition, we also provide support for additional platforms, see System Requirements.

Note that compiling Hippo from scratch needs to be performed against the Java 1.6 target due to a dependency in our stack.

We have tested using the following browser versions:

  • Internet Explorer: 8 and 9
  • Firefox: 16
  • Chrome: 23
  • Safari: 5

Known issues

Currently, there are a few known issues, including:

  • CMS7-6959: External links are opened in Template Composer

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?