Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.
Back up your system before installing a module. Uninstalling a module is not always as simple as removing the file. Modules can add and change configuration in the repository. They may also change content. You should try the module in a test environment first. A module is responsible for updating itself across versions. Keep only one version of each module and its dependencies.
Folders and ZIP files
Choose this option if the module is delivered as a folder or a ZIP file. This type of module is configured completely on the file system.
- Copy the folder or extract the ZIP into the
Magnolia scans the directory periodically and registers the module. It also detects new and modified templates, dialogs and resources.
magnolia.resources.diris a property defining the directory from which resources are loaded in a Magnolia instance. This directory is used for file-based resources such as light modules and for overriding classpath resources. The property is configured in
WEB-INF/config/default/magnolia.propertiesand has the default value
$magnolia.home/modules. To see the current value of the property, go to the Config Info tab in the About Magnolia app.
You can use symbolic links (a.k.a symlinks or soft links) in the resources directory to include light modules located elsewhere on your system.
Choose this option if the module is delivered as a JAR file. All modules provided by Magnolia International are JAR files.
- Stop Magnolia.
- Copy the JAR files into the
- Start Magnolia.
- Open a browser and go to Magnolia AdminCentral
- Run the Web update.
Choose this option if you have your own bundle. Using Maven to manage module dependencies is a best practice.
dependencyelement including the module version number in your bundle's parent POM:
dependencyelement without the version number in the Magnolia webapp POM, typically inside the parent project: