Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
Livefyre (discontinued)
Score 8.2 out of 10
Enterprise companies (1,001+ employees)
Livefyre was acquired in 2016 and became part of the Adobe Experience Manager suite of products. The product has since been discontinued, and is no longer available for sale.
N/A
Pricing
Drupal
Livefyre (discontinued)
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Drupal
Livefyre (discontinued)
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Required
Additional Details
—
—
More Pricing Information
Community Pulse
Drupal
Livefyre (discontinued)
Features
Drupal
Livefyre (discontinued)
Security
Comparison of Security features of Product A and Product B
Drupal
8.1
74 Ratings
1% below category average
Livefyre (discontinued)
-
Ratings
Role-based user permissions
8.174 Ratings
00 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Drupal
7.6
69 Ratings
2% below category average
Livefyre (discontinued)
-
Ratings
API
7.264 Ratings
00 Ratings
Internationalization / multi-language
8.160 Ratings
00 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Drupal
6.5
78 Ratings
18% below category average
Livefyre (discontinued)
-
Ratings
WYSIWYG editor
6.171 Ratings
00 Ratings
Code quality / cleanliness
8.175 Ratings
00 Ratings
Admin section
6.878 Ratings
00 Ratings
Page templates
5.577 Ratings
00 Ratings
Library of website themes
5.468 Ratings
00 Ratings
Mobile optimization / responsive design
6.572 Ratings
00 Ratings
Publishing workflow
6.876 Ratings
00 Ratings
Form generator
6.372 Ratings
00 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.
I was strictly the implementor of Livefyre (for my company only). That task alone was at least 3 weeks worth of work. From a user standpoint, Livefyre is a good product which is why this review is strictly about how difficult it was to implement. Therefore, if a colleague was to ask me if I recommend Livefyre, it's not a straight answer. Questions like, 'how fast do you need it?', 'how centralized is your user database?', 'do you want social login?', all come into question and were details that made my job not easy (hence, my review of 5/10 for suggesting it to others). Once implemented, Livefyre is a great product (notice my overall review is higher), but based on my experience with implementation, it certainly requires a senior developer's dedicated time and patience to set up exactly as desired. For smaller companies with small/simple user bases and websites, the process may be more straightforward, but from my experience, it wasn't out-of-the-box at all.
This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.
Implementation was not easy. Although flexible, I personally wrote at least 1,400 lines of code to get this implemented over a few week's time.
The social login aspect is cool, but again, hard to implement. They did not write any of those modules, although they could have. This required senior-level developmental skills and a knowledge of how social media is interfaced with programmatically. Lots of questions arose from this and it was difficult to implement with virtually no help from Livefyre, other than to provide the hooks into their system for when users were validated. I had to write at least 2 separate login/redirection scripts to accomplish this flow.
CSS tweaking was tricky. We could override lots of common CSS classes, but to get things just the way we wanted it, I ended up writing LOTS of jQuery listeners and functions to transform the output into exactly what we wanted. This was a surprise since the software was sold to us as being 'fully customizable'.
Documentation was sufficient, but not great. Getting the flow of the callbacks that are fired wasn't clear at first, and sometimes did not work as expected.
It should be noted that, after this review was published, Livefyre contacted me stating they now have better documentation and process for implementation (for version V3, specifically) and urged me to revise this review. However, I can only write of my experience with V2, and it WAS difficult to implement over 3 weeks of dedicated time. Another developer on my team implemented version V3 and his evaluation is very similar to mine, claiming much difficulty with the CSS customization.
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
We feel we have a real partnership with Livefyre and we both make each other better. Their customer service has been phenomenal even during a time of rapid growth.
As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.
We felt Livefyre was more innovative and better at SEO. It felt like we were working with a partner for the long haul who was interested in our business and how to improve it.
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.