Page History
...
Update to your latest minor release version first before upgrade to recent major release. A June 2018 example: a customer is considering an upgrade from 5.5.8 to 5.7. The correct sequence would be: 5.5.8 →
→Artifact resource link rangeHigherVersion 5.6 groupId info.magnolia.bundle artifactId magnolia-bundle-parent label $version renderType display_only resourceType POM
→ 5.7Artifact resource link rangeHigherVersion 5.7 groupId info.magnolia.bundle artifactId magnolia-bundle-parent label $version renderType display_only resourceType POM - Update all external libraries required by the Magnolia release to which you intend to upgrade.
- Carefully look for "change" or "changes for ..." sections in the release notes since.
- 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.
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:
..
Anchor | ||||
---|---|---|---|---|
|
...
Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
|
Library updates
.
...
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 | ||||
---|---|---|---|---|
|
...