Discover the release
Check for updates to retrieve the provider’s current signed catalogue. A release has a component, version, compatibility requirements and an explicit identity.
Trusted updatesKeep the CMS current.
Keep the CMS current.
Keep your work your own.
The Update Centre separates the publisher’s reviewed source release from the website content you create. Compatibility and current source are checked before preparation and installation.
Review and prepare
Read the release notes and let the installation check its supported current source. Preparation is a separate step before installation.
Install the reviewed source
The updater applies the signed package through its guarded workflow. Customer content remains separate from the reviewed source change.
Keep the history
The Update Centre retains installed release history and the supported previous-source restore action. Repeated or uncertain operations must be reconciled rather than blindly replayed.
When a check stops
A source, trust or compatibility difference is a useful reason to pause. Preserve the exact result and ask the hosting administrator to review it. Changing a key, deleting a journal or bypassing a source guard is not a normal customer update step.
Update acceptance
After installation, refresh the website and reopen the relevant CMS workspace. Check the changed feature on the live pilot before treating it as accepted for broader use.