Magnolia CMS Reviews & Ratings

4/5

“Reliable CMS With Admin Panel Limitations”

Pros : Magnolia stands out in terms of platform integration and content management, particularly when working with multiple sites. The cloud-based services offer a safe way to store and access data, making it easier to manage large-scale projects without worrying about data loss.

Cons : One challenge we faced was with the administrative interface, which didn’t provide enough flexibility when managing user roles and permissions. As our project expanded, the limited capabilities of the admin panel became more evident.

Reason to switch : Our decision was based on Magnolia’s Java compatibility, which allowed us to integrate it more easily into our existing development process.

4/5

“Perfect CMS with Some Gaps in Admin Controls”

Pros : Magnolia offers a reliable solution for integrating with a variety of platforms. The cloud-based storage is secure, and its ability to manage large projects is one of its strongest points. The content security features were also helpful for enterprise-level tasks.

Cons : The administration panel is a bit lacking in terms of features for managing team members. Assigning roles and permissions can be time-consuming, and the options available feel limited for larger teams.

Reason to switch : The main factor in choosing Magnolia was its Java support, which matched the requirements of our existing framework.

4/5

“Enterprise-Ready CMS with a range of features”

Pros : Magnolia’s integration with Java projects and its ability to manage large volumes of content were key factors for our selection. The cloud storage option was particularly valuable for data security and long-term project stability.

Cons : We encountered challenges in the administration section, particularly in managing user roles and permissions. The interface felt basic, and it didn’t offer the range of features we needed to efficiently manage a large team.

Reason to switch : Magnolia was chosen for its Java-based architecture, which was necessary for integrating with the systems already in place.

3.8/5

“Functional CMS With Admin Challenges”

Pros : Magnolia works well with third-party applications, allowing for easy management of multiple sites. The platform provides secure data storage options and is well-suited for handling large amounts of content, particularly for enterprise-level clients.

Cons : One issue we ran into was the lack of advanced options in the administration section. It didn’t allow for much flexibility when managing a larger number of team members, especially when trying to control permissions.

Reason to switch : We went with Magnolia due to its compatibility with our Java environment and the immediate need for a CMS that could manage multiple sites within a single platform.

3.7/5

“Magnolia's Java CMS Met Our Needs But Could Use Improvement”

Pros : Magnolia's Java-based system worked well with our existing tools, particularly when handling more advanced projects. The software was able to meet our team’s technical needs, and their customer service team was helpful during the initial setup phase, which was important to meet our tight deadlines.

Cons : One aspect that could be better is the administration section. It lacks advanced options for managing user permissions and access, making it challenging to organize tasks efficiently. This is especially noticeable in larger teams.

Reason to switch : We opted for Magnolia due to its compatibility with our Java-based projects, which allowed for a smoother integration with the existing tools in use.

3.7/5

“Perfect CMS for Java Projects, needs to Improve User Management”

Pros : It managed content with ease and its cloud storage features provided a secure way to back up and access data remotely.

Cons : One of the main challenges we faced was the administrative interface, which didn’t offer enough control when managing users. This became a problem as the team grew, making it harder to delegate tasks and assign permissions across different groups.

Reason to switch : I wanted to explore more CMS platforms.

3.7/5

“Suitable CMS for Enterprise Projects”

Pros : Magnolia is a capable CMS for enterprise-level content management, with strong cloud support that allows easy backup and access to stored data. Its ability to handle large projects and offer multisite management made it a good fit for us.

Cons : The user interface felt outdated and made managing the project more difficult than it should have been.

Reason to switch : We decided to go with Magnolia due to its compatibility with our Java-based development framework.

3.6/5

“Great CMS for Java Projects, but Admin Setup Needs Improvement”

Pros : Magnolia’s ability to work with other platforms was very useful for our team. Its features for managing multiple sites saved time, and the cloud storage provided peace of mind when it came to content security and backups.

Cons : The administration panel is one area that could be better. We encountered difficulties in managing users and permissions as the team grew, which added unnecessary complexity to the project.

Reason to switch : I was looking for an easy way to assign role-based permission and have better control over our CMS platform.

3.6/5

“Strong Java Integration but Admin Panel Needs More Features”

Pros : Magnolia’s Java-based platform offered strong integration with our existing tools, making it a great option for managing content across multiple sites. The cloud-based backup and data security options provided additional peace of mind, particularly for larger projects.

Cons : The administrative interface didn’t have all the features we needed for managing a larger team.

Reason to switch : Magnolia’s ability to integrate seamlessly with our Java environment was the primary reason we decided to move forward with it.

3.6/5

“Good Java-Based CMS, but Needs More Features for User Management”

Pros : Magnolia worked well for managing enterprise-level projects, and its cloud backup options ensured that our content remained secure. The system is stable and integrates easily with other tools, making it suitable for large teams.

Cons : I haven’t faced any issues so far.

Reason to switch : I wanted to explore more CMS platforms apart from Umbraco. So, we decided to switch to Magnolia.