Liferay Digital Experience Platform Reviews

Liferay is a good product and can reduce time and cost on project implementation. Liferay opens the door for most problems of our customers. If you have digital problems in your organizations, Liferay already solves more than 80% of them.

Most of my Liferay experience is working on projects to solve other organizations’ problems and meet their requirements. With one of our projects, I used Liferay as a document management solution. With Liferay, users are happy with its ability to manage digital documents.

I would like to see an improvement on the Ecommerce platform.

We have used this solution for over five years.

I did not encounter any issues with stability.

I have experience on enterprise and community versions with HA implementations for less than five servers. So far, I did not face any scalability issues.

I would give technical support a rating of 9/10.

We used Microsoft SharePoint and IBM WebSphere. They are not straightforward and have a complex user experience as a developer.

The setup is straightforward.

The solution has a good ROI.

The solution is inexpensive.

I suggest getting this product. It is easy to use and has a big impact to reduce implementation time. It is not just a product solution. It also has excellent features as a development platform.

Aggregation and personalization (think dashboards) are the really unique selling points of a portal. If you don't need those, you don't need a portal and there will be other libraries or frameworks that are better suited to solve your problem.

We are not really using it ourselves.

The easy, straightforward cases are usually the only ones that are documented. Once you need to do something a little more advanced, you usually won't find any examples and will have to resort to looking through the code to find a place where they do something similar and figure out how it works by stepping through that in a debugger.

They also really like to create new libraries to do stuff (AlloyUI, Metal.js, Senna.js, etc.) instead of seeing what is already available and trying to adapt that for portal use (and possibly committing that back). And lastly, we've run in to a lot of bugs that tend to come back in every version. Things get fixed in one version and after upgrading you run into the same bug again.

I have about 8 years of experience with the product. I've worked with late 5.x versions up until the 7/DXP version now. I'm also a Liferay Highlighted blogger (https://web.liferay.com/web/fimez/blog) and I presented at Liferay Devcon last year.

We didn't encounter any real stability issues, only regressions and bugs.

We didn't encounter any real scalability issues, only regressions and bugs.

Technical support is better than most.

We previously used Sun Java System Portal Server. We switched because Sun Portal just plain sucked.

Initial setup is as easy as downloading, unpacking and starting. No hassle.

Always use the Enterprise Edition, as it isn't worth your own time to try and hunt down bugs in the Community Edition, and there are lots of bugs/regressions.

We looked at JBoss Portal and Pluto.

Only use it when you really need a portal and don't use it as an application framework. In that case, it only complicates your development and performance needlessly.

We tried the 'eat your own dog food' approach and used Liferay for our company's website, but Liferay just isn't meant to build websites. It wasn't easy/simple enough for normal web content editors to add or change content. It is also hard for our designers to create cutting edge designs that can be easily integrated into Liferay as a theme.

• 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.

All the features that are provided by Liferay are very useful, such as Web Content, Document Library and Media, Roles, Permissioning, Resources, Organizations, Users, Sites, Custom Fields, Plugins, and so on. These features enable us to extend Liferay functionality and allow us to customize the out-of-the-box features of Portal to meet our customers’ requirements.

We are using it for projects to provide quick turnaround for our clients' requests. Liferay has a powerful feature for the hot deployment of plugins, and service builders for easily creating tables using Sprint, Hibernate, JPA, etc.

I would like to see them arrange more symposiums in India, because most of the resources who work on Liferay are from India, more than any other country.

I'd like for them to have more interactive sessions, training or face-to-face meetings with the Liferay core team for Developers, so that we can have our questions/clarifications clarified directly with them, rather than asking over a webinar session, through forums, through support tickets, etc.

I have been using Liferay for the past 10+ years now and I love to work with it.

I have not encountered any serious stability issues, but if we come across anything, we get great support from Liferay as a patch.

The portal is very easy in terms of adding more nodes to a cluster.

Technical support is 9/10.

I have used two other portal servers. I really did not like the way they allowed admins to do administrative actions. Liferay is easy to understand and complete the admin actions through the control panel with meaningful names and a short description about what each module does.

Initial setup is straightforward and I did not find it difficult. Liferay has great online documentation, which gives us more confidence in achieving anything with it.

It is a budget-friendly solution and less expensive than any other portal servers available on the market.

Go with this product, because there is great support from the company, rich forum support and online documentation, and the source code allows you to make changes on your own with an LGPL license from vendor.

The most valuable feature is management and permissions according to user, role, and group.

There are several areas that need improvement:

• The core code base needs refactoring. It’s very hard to understand it when trying to do customizations.
• They could remove the business logic from the UI (JSPs) and stop using scriptlets in JSPs.
• Data integrity should be at the database level (normalization/foreign keys) and not at the application level.
• Also, they need to upgrade third party libraries (e.g., Spring) to the newest versions. Liferay is stuck on Spring 3.2, while Spring 4.3.x is the last version and they are working on a 5.0 framework.
• Use Java Config instead of XML config.
• Add support for JBoss EAP domain mode
• Source code sharing in SVN/git still needs to be revisited

I’ve used Liferay for more than 1 year.

Yes, we did have issues with stability.

Yes, we encountered scalability issues.

Initial setup was complex compared to IBM WebSphere.

I recommend going with the CE version.

We evaluated IBM WebSphere portal, but found WebSphere to be overkill for our project.

I would emphasize using Liferay’s OOTB features so you don’t build something that already exists.

Also, make sure you actually need the features it provides.

The features I find valuable are its integration points with other systems and scalability. This is important because the portal (Liferay) is an addition to the current J2EE Framework. That being said, it lends itself to roll all processing (Spring batch) into the Liferay Tomcat bundle. This process can be done in reverse order to ensure performance.

For integration points using simple plugins with SAP, you can create your own secure service bus for information. If you would like to convert your Liferay platform to a presentation layer for CRM, you can leverage Dynamic MS CRM or SugarCRM with ease using plugins or a Java framework.

Our organization benefited by the automated client setup and an easy CMS setup.

Major upgrades switch the Liferay framework core structure dramatically in EVERY occasion. However, there were only subtle changes from the last minor upgrade to the major upgrade.

I used this product for two years where I currently work. In my former job, I used it for six years.

I have encountered stability issues during the upgrade process from 5.2 EE to 6.1.XX EE. There are always issues with Social Office.

We had no scalability issues.

The technical support need was moderate as the tool lends itself to be customized away from the (out-of-the box) OOB portal product. Liferay does not always support these custom components.

We used ColdFusion for a previous project for a CMS portal.

The installation was simple on a Linux-based operating system. It was complex with Windows Servers, but we still managed.

We recommend never leveraging static components when developing licensing requirements because the operating system layer and its environment will always change to fit support costs.

We did not evaluate alternative solutions.

Make sure you understand what you want the product to do. If your company has an overall future for growth, then Liferay is a good choice as it is an enterprise solution.

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.

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.

• Support OSGi Framework
• Excellent Content management system
• Administrative functions through the control panel
• Elastic search

These features are valuable because they all are basic requirements for all portals and have been achieved easily with the Liferay DXP portal.

You

Very important changes are OSGi modularization for existing portlets and new modules. It change the way of development and make life easy for developers

I have been playing liferay from last 9 years and palyed almost all the version and have seen many pros and cons across versions.

Yes we faced many issues during production deployment and specially performance tuning and best suppoprt architecture.

Yes as this is open source so don't see its big hurdle here.

I have not encountered any scalability issues.

10/10

Technical support is very nice for the EE customers.

I did not previously use a different solution.

If its first time then you will definatly struggle but later on it would be very easy if you understand the structure.

It should maintain a competitive price in the open source market.

Before choosing this product, I did not evaluate other options.

It is just awesome; you should experience DXP. I am blogging many useful solution on www.liferaysolution.com

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.