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.
Since Magnolia 5.6, the Activation module has been deprecated in favor of the Publishing module, which is now the default implementation for content publishing functions in Magnolia.
The Activation module publishes content from an author instance to a public instance, see the Activation overview page for more information about how activation works. In the Enterprise Edition of Magnolia, the functionality of this module is extended by the Transactional Activation module which ensures synchronization of content between multiple public instances. The module can be replaced with the Publishing module, which offers a neater and more logical structure of publishing (activation) functions.
Installing
Maven is the easiest way to install the module. Add the following to your bundle. The parent POM of your webapp project should set the latest version of the module automatically. Should you need to use a specific module version, you can define it using the
<version/> in the dependency.<dependency> <groupId>info.magnolia.activation</groupId> <artifactId>magnolia-module-activation</artifactId> </dependency>
Configuration
The Activation module is configured in Configuration > /modules/activation .
Activate and deactivate commands
Users typically activate content by clicking Publish in the Action bar. The click executes an activate command which pushes the content from the author instance to subscriber instances. Conversely, when users click Unpublish the system executes a deactivate command which deletes the content from public instances.
The activate and deactivate commands are configured in /modules/activation/commands . The default catalog contains commands which just publish the content without versioning. Magnolia also provides a versioned command catalog. It contains identically named activate and deactivate commands which first version the content and then delegate to the default commands.
| Node name | Value |
|---|---|
| info.magnolia.module.activation.commands.ActivationCommand | |
| info.magnolia.module.activation.commands.DeactivationCommand | |
| info.magnolia.commands.impl.VersionCommand | |
| true | |
| info.magnolia.commands.DelegateCommand | |
| default-activate | |
| info.magnolia.commands.impl.VersionCommand | |
| true | |
| info.magnolia.commands.DelegateCommand | |
| default-deactivate |
To use one of these commands, define the catalog and the command name in the action definition. See an example in Executing commands with actions.
Activation log storage
The activationLogStorage property defines where information about activations are logged. The default implementation MemoryActivationStorage keeps the information in memory.
| Node name | Value |
|---|---|
| info.magnolia.module.activation.monitor.MemoryActivationStorage |
How activation works
How activation works is described on the Activation overview page.
Troubleshooting
Overview
Content Tools