Liferay Digital Experience Platform Reviews

All of the following features are important to us:

• Content Management System
• Document Management System
• Workflow Engine
• Roles and permissions for authorization and authentication
• Forums, blogs, and chat
• Responsive UI

They are all in high demand, and we have implemented them for our customers.

We use the Workflow Engine for managing the approval process. We have used blogs and discussion forums for information exchange between the employees, and as a chatting platform within the organization.

The loading speed could be improved.

I have been using Liferay Digital Experience Platform for about 10 years.

We did not encounter any issues with stability.

We did not encounter any issues with scalability.

We received very good technical support. For the Enterprise Edition versions, there is exclusive support. For the Community Edition versions, there are a lot of forums available.

Before using Liferay Digital Experience Platform, we used WordPress. Liferay is far more secure and robust.

The initial setup was pretty straightforward.

The Community Edition versions are open source and freely available.

Pricing for Enterprise Edition versions can be obtained by requesting a quote from Liferay.

We evaluated both WordPress and Drupal before deciding on Liferay.

This product is very secure, robust, and highly scalable. It can also be customized to almost any extent.

We have developed some outlets to manage some specific requirements for public administration and we use this solution to assist.

The solution is easy to install.

There's a lot of plugins. It's an enterprise-level solution that is ready to use almost immediately and users can immediately share and collaborate once they've installed the application.

It's one of the best platforms I've used.

The documentation provided needs to be more detailed. It's sometimes hard to develop things because the documentation is so sparse.

The forums should have more content and cover more areas of the solution. It's also not so easy to navigate through it.

I like to participate on some of Liferay's symposiums in Italy. We've found the company to be managing the architecture in Italy quite well, and we've been quite satisfied with them.

I've also worked on Tableau, which is a social platform. Tableau is quite lightweight and easy to use, but the community is smaller. Liferay has a big community at the moment.

The initial setup is straightforward. We found it to be quite easy to install, and very quick.

Liferay is an expensive solution.

The solution is quite expensive, and, in the Italian market, it may be a barrier to entry for many companies.

I'd rate the solution eight out of ten. It's a good platform that's easy to install and easy to start to use. It's also easy to customize if you are only going to customize some CSR. Although I've never tested it, I know now that it's possible to have access to more direct APIs.

I like most of out-of-the-box features, especially the control panel features.

There is no need to develop from scratch. The framework is ready for development. It provides multi-tenancy and is easy to integrate with other applications.

The front-end technologies need improvement.

I have used Liferay for eight years.

We did not encounter many problems with stability.

We did not need to make any changes to support our work for a long time.

I would give technical support a rating of 3.5-4/5.

We traditionally build applications from scratch. This makes basic setup, such as user management, organization, roles, and permissions easier. It is easy to extend or customize out-of-the-box features.

It is easy to set up for any environment. Instructions are available over the internet.

I did not get a chance to work with sales.

We did not really evaluate other options.

Liferay, Version 7, gives OSGI implementation. This is the future of Java technologies. Liferay enables you to stay with latest technologies with each version release.

Definitely CMS. Tons of features are available for content management:

• Structures
• Templates
• Application display templates
• Asset publisher
• Staging
• Page management

These features have become well evolved over time.

It is very easy to pitch Liferay to any client. This is due to the wide array of functionalities it has and in terms of what it has to offer.

Liferay always delivers as follows:

• Setting up an intranet portal
• Making some public facing website
• Creating a collaboration platform

Documentation needs improvement. But this too has evolved over time and is still a work in progress.

I have been using Liferay for more than eight years.

Every major version has some stability issues, but that is the case in every product. Liferay has undergone a major overhaul in its DXP release, which has introduced some stability issues. From my experience, these issues will cease to exist after one or two minor releases.

We have not had any scalability issues.

Support is fair enough. I have seen that the technical support varies based on the region where you purchased the product.

For example, technical support in Europe and the Americas is very, very good. These regions have very good technical folks.

We didn’t have anything before Liferay. I had analyzed JBoss Portal in 2008, but I then went ahead with Liferay and I have never turned back.

The setup is fairly simple. You can set it up by the time your coffee is brewed.

Compared to other big players in portal platforms, Liferay's pricing is very competitive. And remember, the latest version of Liferay is not just a portal framework, but it is a digital experience platform which offers way more.

I evaluated JBoss Portal in 2008, but I then went ahead with Liferay

Go ahead with Liferay DXP. There is a lot of expertise in the market with this product. It is arguably the best Java-based portal platform out there.

• Portlet development technology promotes re-usability of code (one portlet can be used in many portals).
• Very powerful product for Intranet solutions.
• Multi-instance capability.
• Document management and its permission system is very powerful.

It helps develop intranet solutions with code re-usability; once you develop a portlet, you can use it for any number of different solutions.

Its marketplace provides many out-of-the-box functionalities.

Architecture is so good that you can fit many organizational structures into Liferay.

• Documentation
• Mobility
• Theme development is tough for UI guys. A UI guy needs to learn to work with Liferay.

I have been using Liferay 6.2 for the last two years and Liferay Digital Experience Platform for the last three to four months.

As for now, Liferay DXP was just released, so there are many issues. Things don't work as mentioned in the documentation. It will get stable in the next releases. Liferay 6.2 was quite a stable version.

We haven’t had any scalability issues.

I rate technical support 8/10.

I was not previously using any other solutions.

Initial setup is not very complex, but you need to follow the exact steps they suggest and it’s not that easy.

No advice as of now.

Check your requirements and license costs. If you are going with a licensed version, try to map your functionalities with Liferay. Then decide whether you need Liferay or not.

The most valuable features are role-based permissions, organization management, and the scalability of many third-party integrations.

Liferay has a CMS, role-based permissions, and hierarchy-of-organization community management which provides lots of features for intranet and enterprise applications. It also provides tools for mobile development.

The API documentation could be improved, as well as the debugging tools.

I’ve used Liferay for more than 6 years.

We had a number of issues with stability, but we found solutions from the community or in patches for the enterprise edition.

We did not encounter any issues with scalability.

We didn’t use any other solutions.

The initial setup was quite easy.

We evaluated WebSphere before choosing Liferay.

For normal sites, we can use other available options, such as PHP. But Liferay is good for enterprise and large-scale systems, especially role and hierarchy management systems, or when you have multi-site requirements.

The community and collaboration features such as forums, library, wikis, event and ideas.

Our organisation is set up to support other organisations working in Public Sector Improvement. The product has helped our members and communities to freely connect, share knowledge, develop initiatives and share expertise in a secure environment. This has enabled organisations to save both time and money, generated and incubated ideas to drive improvement, and helped members discover knowledge to help in their job and connect with people and experts.

Liferay does currently lack a good integrated analytics package, automation, and filtering.

I've been using it for years.

We had no material issues during deployment.

We did, at different stages, have performance issues, but this was resolved by moving to the recommend infrastructure.

It's been able to scale for our needs.

8/10

9/10

We previously used an IBM WebSphere product. We moved to an open source product to support the concept being promoted in the UK Government and expected scalability without scaled cost.

A bit of both. Learning what a new platform can and can’t do can take a while especially if you are moving from an established platform that was bespoke built to a portal based platform. Showcasing the benefits of moving to the members and migrations was tough to start with but has proved to be beneficial.

We implemented it through a vendor team, PFI Knowledge Solutions Limited (PFIKS). They are the only UK platinum partner of Liferay and have a great level of expertise - 8/10, even though it is a relatively small organisation

Check out the community (free) version first. Go with Enterprise Edition for the great Liferay support.

A number of alternative products were evaluated, including staying with the original IBM platform. We selected Liferay due to its flexibility and scalability.

Take your time, Liferay can do so many different things and can be very complex. So be clear on what you are building.

For me, the most important features are scalability, architecture, the fact that it's Java-based, includes a CMS, and provides audience targeting tools. The newest Liferay "Screens" feature is very interesting too.

We develop advanced web solutions based on Liferay with lower development costs and fewer team members.

Liferay needs a better web content search engine.

I've been using Liferay since 5.2.x version in 2009.

We have stability issues only when the developers don't follow the Liferay guidelines and best practices.

I didn't have any issues with scalability.

Liferay has good technical support with a high level of product knowledge.

I’ve tested several options over the years: PHPnuke, PostNuke, Joomla, WordPress, Drupal. But none of them have as many built-in features as Liferay.

Liferay bundles make the initial setup is very easy. Just execute a bundled Tomcat package with a Liferay installation within.

It’s a good idea to subscribe to Liferay support. They have good product knowledge and solve problems quickly.

We tried Drupal, but it doesn't have as many built-in features as Liferay.

My advice is that if you want to extend the product, don't recreate existing functionalities or libraries. Just follow the guidelines and best practices.