To Magnolia:
- Stop the application server.
- Extract the new Magnolia bundle.
- Replace JAR files in the
WEB-INF/lib
folder of your old Magnolia instances with new JARs from the bundle. - Remove any module JARs you had previously removed from your instances. Add any modules you might have added.
- Optional: Delete all indexes to give them a little boost. Delete the
index
folder under each workspace directory: repositories/magnolia/workspaces/<workspace>/index
. Indexes are recreated on startup, which might take a while depending on the size of your repository. - If you customized
magnolia.properties
files, compare the changes to the file in the new bundle. Properties may have been added and removed. - Read release notes for all intermediary versions for any
- Restart the application server.
- Using your browser, go to the Magnolia instances and run the Web update.
Recommendations when upgrading Magnolia CMS:
- Update to your latest minor release version first before upgrade to recent major release. For example as of May 2017, a customer would like to upgrade from 5.4.1 to 5.5.4 (latest release at that time), then the correct sequence would be 5.4.8 --> 5.4.12 --> 5.5.4 instead of 5.4.8 --> 5.5 --> 5.5.4.
- Carefully look for "change" sections such as [Changes for 5.4.x users] whereas that changes is necessary in this specific case when you are updating from 5.4.1 solely.
- Because upgrading process takes time and vulnerable to incidents, please minimize the risk by clean up your system, remove unused data, reindex everything and do a full backup first.
#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))