Upgrading a custom CMS from using Hippo CMS release 7.5 to 7.6
New in version:7.6Below 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.
The site (hst) does not need any changes other than version numbers
| Preparation | - | |
| Introduction To Relaxed Node Types |
What are relaxed node types and why should I care? | |
| Relaxed CNDs |
Use relaxed node types for documents and compounds. | |
| Goto Plugin |
Remove the Goto plugin and use the core CMS functionality instead | |
| Upgrade Project POMs |
Upgrade Project POMs from 7.5 to 7.6 | |
| API Changes |
API changes that might impact plugins. |
Hippo Europe: +31 (0)20 5224466
Hippo North America: +1 (707) 773-4646
© 1999-2010 Hippo B.V., All Rights Reserved