Liferay Digital Experience Platform Reviews

The most loved Liferay DXP feature launched is modularity. The modular approach to implementation helps to add enhancements easily.

The collaboration feature of Liferay is a very nice feature that can help to create a website quickly and easily, even by a non-technical person.

Apart from these, I also like the security features provided by Liferay.

Liferay can be used by a non-technical person with minimal training. A content publisher can easily update and add the content. This makes updates available faster for users.

Documentation for the newly launched version is not up to the mark. It would really be a great help for developers if they were to get proper documentation of the features.

I have used Liferay since 2007.

Stability is very well maintained by Liferay. Whenever they fix any issues, they publish it to the community, so we can apply a patch to make it more stable.

Liferay has provided proper guidance for making scalable enterprise solutions. One node of Liferay offers support for an extensive number of users. If the load is growing, we can easily add a node by making cluster environments.

Liferay provides multiple levels of support for their users. When we raise any support ticket, we get a prompt and quick response from their support staff.

I have used Plone, but went ahead with Liferay due to the availability of vast out-of-the-box features.

The initial setup was very straightforward.

Liferay provides a vast range of features with minimal license costs, which makes it better than the others.

Utilize its modularization feature to its best, to make it an easily extendible and scalable enterprise solution.

We only use it for internal, departmental websites. It helped us migrate our company’s EA website from SharePoint to Liferay.

It has increased communication between the departments and their employees.

We found it difficult to upload documents. It seemed unnecessarily complex.

I have used this solution for three years.

There were no stability issues.

There were no scalability issues.

Unfortunately, our company only allowed certain individuals to access Liferay technical support. For any kind of technical issue or training, we had to go through our fellow employees.

I would recommend that more employees get access to Liferay technical support. I would have found that very helpful.

My company was using SharePoint. I am not sure why the switch was made.

The setup was complex. Most people didn’t understand how to convert their SharePoint site to the Liferay platform. Many of them still hadn’t been converted when I left the company.

Line up technical support from Liferay with your company employees from the beginning of the implementation.

• Web content management system: Enables non-technical staff to add/update content that is approved by content approvers in a workflow. Staff is trained to create new sites.
• Integration platform: Integrates existing applications so that users are able to access content in one place.

It has helped our client to quickly set up websites for their external clients.

I am having a hard time getting through the security scans. I wish there were documentation to create some settings that would prevent scanning for each language when you are using a particular language.

I have used this solution for three years.

We have not yet had stability issues.

We have not yet had scalability issues.

We are a consulting company. Based on our clients' requirements, we have used various CMS products, such as Mura CMS, Drupal, and SharePoint.

The initial setup was straightforward.

We are using the Community Edition, so I cannot say anything about this subject.

For content management, we have used Mura which is a ColdFusion based CMS, Drupal, and SharePoint.

If possible, go for the enterprise version as they will have more support.

I really value the out-of-the-box features (portlets/application), OSGi modularity (in the last version), and tools for developers.

We needed to rewrite a legacy application written from scratch with much less developer resources. Liferay was a great choice. It had a big learning curve in advance, but it had great results in the end.

I would like to see better documentation. Updates in the documentation do not follow updates in the code and functionality.

I have used it since version 5.2, in 2008.

There were some scalability issues. Finding a good infrastructure setup is not an easy task. Some scalability issues can arise when changing database engines, since Liferay supports different databases.

I didn't use technical support.

It might sound trivial, but plan all the project phases, in terms of infrastructure and performance testing, well.

Liferay starting from DXP redesign the full software architecture using OSGI (actually since 6.2 is integrated but just for small integration points). With this new design, they gain the possibility to updates released version more frequently and also "components by components." From a point of view of a developer this is a great improvement by the way after first general available release. Liferay also released public documentation, allowing developers build custom plugin and general customization. This documentation gets outdated in different parts after some new release (GA2 ,etc).

The most valuable features is Java based platform and JSR portlet for development.

It has provided one place for integration.

There are a lot of possibilities for improvement in several areas.

I have been using Liferay since 2007

Yes, a wide range of issues.

Yes, in most of our big projects.

Yes, both horizontal and vertical.

Customer service is very high.

Technical support depends on the subscription, but it is good.

No previous solution used.

The platform is independent of the environment and first setup is very easy. Just click.

We used a vendor team who I met and they have great expertise.

Big benefit is in relation to cost. There are a lot of out of box things and on the other side is has got elastic platform for further improvements.

Just the subscription, which is one year for us.

Yes, we also looked at SharePoint and WebSphere.

High cost.

It has a built-in WCMS (web content management system) and provides the ability to develop complex portlet-based web applications. That's valuable because it is Java/Java EE-based and open source.

The documentation could be better.

I have used Liferay for three years.

I did not encounter any issues with stability.

I did not encounter any issues with scalability.

Setup was easy and straightforward.

Hire developers with a high level of expertise with Liferay Portal.

• Scalable
• Easily integrates with other ecosystems
• Fast
• User-friendly
• Speedy development

As it is open source, it has lots of features and it is constantly updating. Therefore, bugs also keep coming. More quality improvement is required.

I have used this product for the last seven years.

I did not encounter any stability issues.

I did not encounter any scalability issues.

Technical support was good.

We previously deployed WebLogic, but we moved to Liferay because it offered a range of out-of-box features. It was also faster than WebLogic.

The setup was easy.

Pricing is less expensive and structured in comparison to other paid portals.

As mentioned earlier, we used WebLogic.

It’s fast, easy, scalable, and stable with a competitive price. Go for it.