7.4 To 7.5

Upgrading a custom CMS from using Hippo CMS release 7.4 to 7.5

New in version:7.5

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 using 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.

Note: Please see Step by Step Upgrading Example From 2.05 To 2.20 for upgrading the HST.

	Preparation	Prepare the upgrade to make sure that nothing is lost in the automated upgrade by the 7.5 repository.
	CMS And Repository Artifacts	The CMS and repository have been split into two independent projects.  Dependencies need to be updated to use the new artifact names.
	Using The New Gallery Imageset	Optional: Convert images to the new gallery imageset base type.
	Enabling Content Translation	Optional: Upgrade content such that it can be translated within the CMS.
	Upgrade CMS Plugins	In the CMS project structure, an API module has been introduced.
	Column Providers In Folder/search View	The columns in the folder and search views are pluggable, making it straightforward to display document / workflow attributes in folder and search views.
	Upgrade The Console Configuration	Reload the console configuration in the repository.
	Upgrade Configuration Editor	Upgrade the HST configuration editor.
	Start The New 7.5	Having build your project, start it using on the old repository data.