Page History

...

Publishing vs Activation and custom commands

The 5.6 branch brings also the new Publishing module pack (s) (see magnolia-publishing-packparent on nexus), which is intended to replace the Activation module ( /modules/activation ) and the Transactional Activation module ( /modules/exchange-transactional ). Besides giving a more logical ordering to the publishing functions in Magnolia, the new module pack also :

...

sets all workspaces as publishable by default.

 If you wish you may still continue using the original Activation modules in the 5.6 branch, but opting for the new publishing module pack means that you have to:

• Remove both the activation modules.
• Add all modules from the magnolia-publishing-pack to your bundle, either manually as pre-built jars or as dependencies.
• Check that after the upgrade the subscribers were correctly migrated from /server/activation to /modules/publishing-core/config/receivers .
• Rewrite your custom activation commands to be compatible with the modules of the new publishing module pack.

Please note that the publishing and activation modules cannot be used side-by-side. Use either only Activation or only Publishing. For further information about configuring the new publishing-core module see the Publishing module page. 

...