Page History

...

• Remove both the activation modules.
• Add all modules from the magnolia-publishing-parent 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.

Replacing publishing with activation

Using activation is still possible, but only after replacing the Publishing module and the Publishing Transactional module with the Activation module and the Transactional Activation module, respectively. You can do this in two ways:

• Remove all the publishing JARs from the ../WEB-INF/lib folders of your author and public instances. Add the activation JAR files in their place.
• Exclude the publishing dependencies from the POM and add the old activation dependencies.