Page History

This page contains the information you should be aware of when upgrading to Magnolia 5.6.x from any previous and currently supported version, see the End-of-Life policy.

Before starting the upgrade, please read the release notes for the version you are updating to and all intermediate versions, the general upgrade procedure and the specific aspects. If migrating from Magnolia 4.4/4.5, please read migration documentation first. You can also contact us for migration support. 

General procedure

1. Stop the application server.
2. Extract the new Magnolia bundle.
3. Replace JAR files in the WEB-INF/lib folder of your old Magnolia instances with new JARs from the bundle.
4. Remove any module JARs you had previously removed from your instances. Add any modules you might have added.
5. 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.
6. If you customized magnolia.properties files, compare the changes to the file in the new bundle. Properties may have been added and removed.
7. Read release notes for all intermediary versions for any additional update tasks.
8. Restart the application server.
9. Using your browser, go to the Magnolia instances and run the Web update.

Recommendations

1. Update to your latest minor release version first before upgrade to recent major release. A June 2018 example: a customer was considering an upgrade from 5.5.8 to 5.7. The correct sequence would have been: 5.5.8 → 5.5.10 → 5.6.6 → 5.7

   Info
   title Why we go that way?
   Because when a customer reports issues when migrating from 5.4.6 to 5.5, for instance, then we will support a workaround/patch and later release the fix also in 5.4.7. The fix of the issue in 5.4.6 when migrating is usually located in version handlers. Then at some point, we drop 5.4.x because of an outdated technology stack (such as Java versions and security support from third-party libraries), upgrade to 5.5.x, and the process repeats. So going with the latest release of each major release will free you from the issues and bring you the improvements.

2. Update all external libraries required by the Magnolia release to which you intend to upgrade.
3. Carefully look for "change" or "changes for ..." sections in the release notes since.
4. Because the upgrade process takes time and is vulnerable to incidents, please minimize the risk by cleaning up your system, removing unused data, reindexing everything and doing a full backup first.

Adding the new privacy modules

If you have an Enterprise Pro license - add the new Privacy modules which helps you to adapt your websites compliant with the General Data Protection Regulation (GDPR).

The magnolia.properties file

When upgrading Magnolia - its is always worth to compare your magnolia.properties file with the one coming from freshly released Magnolia bundles. 

Here are the latest versions:

Magnolia CE:

..

Magnolia EE Standard:

..

Magnolia EE Pro:

..

WebDAV removal

...

Anchor
anc-known-issues anc-known-issues

Known issues

Other issues

For other known issues please see the Known issues page.

Further reading

• Migration from Vaadin Framework 7 to Vaadin Framework 8
• Upgrading to Vaadin Framework 8 (Part 1 of 2) 
• Upgrading to Vaadin Framework 8 (Part 2 of 2)