Update Existing Content Items
Update existing content items in a particular environment (e.g. production) as part of a new release.
No content items in the target environment are being edited.
No content items in the target environment have outstanding publication requests.
Writing Updater Scripts for existing content items
When deploying a new release it is sometimes necessary to update existing content items. Some example use cases are:
- A new field with a non-empty default value is added to a document template. The default value must be added to existing documents.
- A new variant is added to an image set template. The new variant must be added to existing image sets.
The procedure is as follows:
- Inventorize which content types need to be updated and what changes need to be applied to content items of those types.
- Write an Updater Script to make the required changes using the Updater Editor in your development environment.
- Test the Updater Script on a relevant set of content in your development (or test) environment.
- Once you are satisfied, add the script to your project's bootstrap module so it will be added to the updater registry (JCR path /hippo:configuration/hippo:update/hippo:registry) on deployment in the target environment.
- Prepare the release as usual and release the required artifact(s).
- Deploy the release artifact(s) in the target environment.
- An administrator runs the Updater Script in the target environment. The affected content items will be updated.
- Existing content items in the target environment may need to be updated when a new release is deployed.
- Updater Scripts can be used to update existing content items.
- Updater Scripts are developed in the development environment.
- Updater Script are packaged with the release artifact(s).
- Updater Script are executed by an administrator in the target environment.