7.2 To 7.3

Upgrading a custom CMS from using Hippo CMS release 7.2 to 7.3

New in version:7.2

Below you find a list of upgrade steps. If your project includes some specialities you may have to do some extra steps. You can ask your questions on the Hippo CMS forum.

Only an upgrade of the CMS is covered in these pages. If you want to make additional changes to document types or configuration, these should be postponed. When the upgrade has completed, you can start the update, either by the CMS itself or by restarting with your own upgrade module. When using a clustered deployment, make sure that only a single node of the cluster will perform the upgrade by stopping the other cluster nodes. Clear the journal table in the database and index files when restarting the other cluster nodes after the upgrade.

	Preparation	Prepare the upgrade to make sure that nothing is lost in the automated upgrade by the 7.2 repository.
	Upgrade Project Content	How to upgrade the initialization xml and cnd files to 7.3. These are the files containing initial content, document types and templates.
	HST Configuration Editor Upgrade	Update the HST Configuration Editor.
	Migrating Mandatory Fields To Required Ones	With the release of CMS 7.3, required fields are introduced. These fields are less strict than the mandatory JCR keyword. This makes it possible to persist partially completed documents.
	Upgrade Browser Sections	The integration of search with browsing has necessitated a number of changes in the way sections are added to the browser perspective. In this section, you'll learn how to update your own sections to function in this new setup.
	Upgrade Plugins To Use Wicket 1.4	The CMS has upgraded to Wicket 1.4.x, that offers generics to component developers. Any existing Wicket plugins have to be upgraded to be compatible with the Hippo CMS 7.3 release.
	Upgrade The Maven Pom Files.	Update version numbers in the project pom.
	Repository Configuration	If you have customized or copied the repository.xml configuration you need to make that your configuration.xml is kept in line with the repository.xml as delivered by Hippo. Even without customizing the repository.xml, parts of this file are duplicated on your filesystem and this documentation described how to update this configuration file on your local filesystem.

Hippo Europe: +31 (0)20 5224466
Hippo North America: +1 (707) 773-4646