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
Oracle Social Cloud (legacy)
Score 7.6 out of 10
Enterprise companies (1,001+ employees)
Oracle Social Cloud helped marketers to discover, analyze, and respond across paid, owned and earned social channels to measure the impact of their data-driven campaigns. Oracle Social Cloud is a legacy product, and no longer available for sale.
N/A
Pricing
Drupal
Oracle Social Cloud (legacy)
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Drupal
Oracle Social Cloud (legacy)
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
—
More Pricing Information
Community Pulse
Drupal
Oracle Social Cloud (legacy)
Features
Drupal
Oracle Social Cloud (legacy)
Security
Comparison of Security features of Product A and Product B
Drupal
8.1
74 Ratings
1% below category average
Oracle Social Cloud (legacy)
-
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
Oracle Social Cloud (legacy)
-
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
Oracle Social Cloud (legacy)
-
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.
If you are looking to manage multiple social channels and quickly schedule posts it's a great tool. Not the best tool if you're looking to provide real time or near real time support and feedback to customers who are in the moment.
The ability to schedule months of content at a time and view it across a calendar.
The approval process - you can set up teams to create, edit, publish, approve etc.
The content and apps module allows you to create modules which can be displayed on your Facebook page under the tabs section. You can create interactive modules for your customers to view.
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.
Videos posted to Facebook via SRM have to be clicked to run instead of running automatically.
No ability to boost posts or ads from SRM.
Due to privacy restrictions of various social streams, unable to listen to 'people'; can only listen to business pages.
Not able to publish the same post at the same hour across time zones. So, if you want to publish a post at 8 am EST and 8 am PST, you have to do 2 separate posts. Otherwise your 8 am EST will post at 5 am PST.
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.
Our personal support finally came back at the end of our contract, but their product just could not offer what the competition offered. Social media is moving fast, and you need to work with companies that understand that and are at the forefront of trends, you can't get stuck with a company that is standing still.
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.
The personalized support of a single individual who gets to know your business and your needs is priceless. They will assist with anything from a technical glitch to a campaign strategy that has worked for other companies
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.
Vitrue's training was limited online and not very in-depth, but the the platform is overall very easy to use and doesn't necessarily need a large amount of training.
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.
I have used one other enterprise level application; it was comparable to SRM. We moved away from the first application because our parent company uses many other Oracle applications, not because we were 'unhappy' with the application we had at the time. Having said that, SRM does everything we need from it; in fact, there are features we aren't fully leveraging at this point. I especially find Engage, Content and Apps and Publish particularly useful. This is the kind of platform that is very robust; you get out of it what you have the time and resources for
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.
Audience. Before SRM, we had 1,000 Likes on Facebook. In 1 1/2 years using SRM, our Likes have grown to 20,000.
Frequency. Before SRM, we posted once a week on Facebook & Twitter. In 1 1/2 years using SRM, we now post 54 times a month, or about twice a day on weekdays.
Internal acceptance. Before SRM, social was considered "a hobby" by senior management. Now, social marketing is a key part of the strategy of every product launch. That is due to the hard work of our social marketing manager, of course, but her efforts were amplified by SRM.