Liferay Digital Experience Platform Reviews

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.

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.

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

• CMS lets business users to create and manage web content by business users, while maintaining revisions. Liferay enables users to be independent of developers and to be able to manage content within the portal.
• Roles and permissions management gives developers the ability to build persona- and preference-based functionality within the portal.
• Document library
• Plugins, workflows and rules provide flexibility to customize the portal.

• A self-service portal for customers
• An online community to share and get knowledge
• A portal for distributing manuals.

• Ability to create content
• A cloud offering

I have used Liferay for approximately five years.

Liferay is a very stable product (except for version 7, as it is relatively new).

We have no issues with scalability.

Technical support is very good.

We started using Liferay directly. There was no previous solution.

Setup was straightforward.

It is very affordable and licensing is similar to Red Hat Linux, where we pay only for the support.

We evaluated Adobe Experience Manager and WebSphere Portal v6.

Have a complete understanding of out-of-the-box features as Liferay makes most of the functionality required available without any customization.

• Social networking
• Document sharing

We get better communication between team members and faster access to documents.

There is always is something to improve. I welcome improving the DMS camp and more easy collaboration with Microsoft Active Directory.

I have used Liferay for three years.

We have not had stability issues.

We have not had scalability issues.

I didn’t use technical support.

I used more Microsoft solutions and Liferay is a more complex, “all in one” solution.

Setup was not straightforward. The Community Edition was a bit complicated and they should fix the code.

I use the GNU license.

I chose between Liferay, Drupal and Microsoft products.

Liferay is highly scalable and more complex than Drupal. For the same quality, you need more Microsoft solutions, so more servers and more capacity.

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.