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.

The Commenting module is now in maintenance mode and is no longer included in Magnolia bundles. 

Please use the new commenting module, currently available in the magnolia incubator instead

If you are looking for commenting or forum services, you have several options:

  • Magnolia commenting service – Magnolia offers a basic commenting service in the cloud. It's a REST-based service hosted by Magnolia International. The service is secure, contains no advertising, works also for intranet sites and avoids having to cluster the comments in a multi-instance setup. You can connect the service to an on-premises or cloud Magnolia instance. See a live example on Magnolia's own blog. Contact Magnolia Services if you are interested in this option.
  • Third-party integration – Most Magnolia sites today choose to integrate a third-party commenting or forum system. There are several on-premises and hosted services on the market such as DisqusIntenseDebate and Discourse. Forum services have evolved to support features such as badges, reputation management and search engine optimization that are beyond what the Magnolia Forum module offers today.
  • Legacy modules – You can still get the Magnolia Forum and Commenting modules from Nexus for your own Magnolia bundles. The Forum module also requires the magnolia-core-compatibility .jar to be in the classpath to function properly. 

If you insist in using the old Magnolia module:

See using commenting for more information.

The Commenting module adds a commenting functionality to any Magnolia page. 


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.