Magnolia 4.5 reached end of life on June 30, 2016. This branch is no longer supported, see End-of-life policy.
Magnolia ships with activation and deactivation (deletion) approval workflows by default. These are provided by the Workflow module. Disabling the workflow may be appropriate for a simple site workforce where there are no separate editor and publisher roles. When the approval workflow is disabled, content will be published to public instances immediately when activation is launched.
Removing the Workflow module disables all workflows, not only the content approval workflow. Don't remove the module if you have custom workflows used for some other purpose.
If you did not install the Magnolia instance yet, choose this option. Disabling workflow involves removing the Workflow module .jar file.
To disable workflow before installing Magnolia:
magnolia-module-workflow.jarfile from all instances. The .jar file is in
If you already installed Magnolia and want to disable workflow after the fact, choose this option.
To disable activation workflow on an existing, already-installed and bootstrapped Magnolia instance:
activatecommand chain with a single
classdata node and set its value to
The command should look like the default
activate commmand in
modules/adminInterface/commands/default/activate which simply activates content immediately without starting an approval workflow.
To disable deactivation (deletion) workflow on an existing, already-installed and bootstrapped Magnolia instance:
deactivatecommand chain with a single
It should look like the default
deactivate commmand in
modules/adminInterface/commands/default/deactivate which deactivates content immediately without starting an approval workflow.