7 CRM Options Compatible with Drupal

Chris Ward takes a look at seven CRMs compatible with Drupal:

What has a CRM got to do with Drupal? Nothing directly, but indirectly if you’re looking to streamline your business operations and automate the ways people can interact with you, your CRM will need to work well with your website.

If you are reading this, I will assume your website is likely built in Drupal and, unsurprisingly, Drupal continues its talents of playing well with others into the domain of CRMs.

In this article, we will look at several of the big players in the CRM space that work well with Drupal, how they integrate or how developers can get them to integrate.

The most compatible is RedHen which is written with Drupal it self, so it is Drupal. But each one of them has their own advantages and disadvantages.

Drushful Thinking

Mike Crittenden gives an intro to drush, but even people who have been using drush a lot can learn things from this post:

If you’re asking that question right now then congratulations! You are one of the lucky people who will have your life changed today! Cancel everything and read up on Drush, the command line bridge to Drupal.

Everybody knows about Drush, ya Dingus!

That’s more like it. Who doesn’t love Drush, right? Right!

But more and more, I find myself seeing people reinventing things that Drush already handles because they just don’t know all that Drush can do. It’s getting frustrating, and I want to fix that.

Easily upgrade your image fields for retina

Chris Free blogs about upgrading to retina quality images:

Out of the box, you don’t really have a lot of good options. You could simply upload high resolution versions and force your users, regardless of display type to download massive file versions, but that’s not exactly the best for performance. You could use some custom field theming and roll your own implementation of the element, but browser support is basically null at this point. That won’t do. You could do what Apple does and force the browser to download 1x versions of your images then use javascript to detect high resolution displays and then force the browser to download all of the high resolution versions…I think you see my point.

What if you could create hi-resolution versions of these images without a ton of added filesize overhead? What if you could do this all within Drupal? No special coding, no uploading of multiple versions, no special field templates or unnecessary javascript. Just a basic Drupal image field with a special image style defined.

aGov: First Impressions of Australia's Government Drupal Distro

Sam Becker writes about aGov, a Drupal distribution built and maintained by the Australian Drupal shop PreviousNext:

The distribution is a foundation for websites built for government organisations. At Code Drop we've been involved in the development of websites for government bodies locally in WA, however it is an area that is forecast to expand significantly and one that all Drupal agencies should be embracing.


he distro is packaged with 9 default bundles which cater to all of the typical government content requirements you might expect to find. The out of the box content admin experience is highly polished and well considered with searchable taxonomy select lists, great media management and sane WYSIWYG defaults.

Worth checking out.

Drupal images: how to improve the user experience

Paul Rowell blogs about images in Drupal:

Image management doesn't really exist in Drupal core, one way to improve this is with the media module. I've mentioned the media module before in a post about improving the content editors ux, it's a module that allows you to more easily manage images uploaded to the site. With this installed you can reuse images without needing to upload them again, search uploaded images and easily switch between all images and only images you've uploaded. It's a little rough around the edges but works wonders in making image management easier.

He continues with with a useful list of extensions, for example multiple image upload, response images, cropping and resizing.

Amazon S3 module in drupal

Manikandan writes about the Drupal S3 module. This allows you to put all content under sites/default/files on S3.

The AmazonS3 module allows the drupal local file system to be replaced with S3, where the files can be uploaded or downloaded from S3.

Future-proof your Drupal 7 site

OSTraining posts on the modules you should use today to make upgrading to Drupal 8 easier:

Over the last few months, Dave Reid, one of the most active Drupal developers, has been giving a presentation called "Future-proof your Drupal 7 site".

He comes up with a list of modules that have been backported to Drupal 8. Using those modules means you won't have to re-train your staff for Drupal 8.

Dave also has some recommendation for modules to avoid, because they've been replaced by alternative solutions in Drupal 8. Here are 6 modules that might be worth avoiding if want an easier update to Drupal 8 in years to come ...

Getting Started with Behat

At Xplain Hosting we love Behat. David Lanier has an introduction how to get started with Behat:

Suppose you build a site, it works great, the client loves it, you launch it, and the client still loves it. Yay! Now life goes on, and six months later, the client comes back to you saying they see a red box when they are logged in, with a message about security updates. You look and see that Drupal core, ctools, rules, views, commerce, date, and a handful of other modules have updates availalbe. Some are security updates, and others are bugfix/feature updates.

So you want to update this code to resolve security issues and improve the functionality of the site. But how can you be sure that these code updates will not hurt or break any of the existing functionality? You could revisit all of your feature work from six months to a year ago and confirm that those features still work as intended. But that can be time consuming and disrupt your other work.

So how do you make updates, whether updating contrib code or doing new custom work, with confidence that you're not breaking essential funcionality and without wasting countless hours doing a bunch of manual testing?

Future-Proof your Drupal 7 site

At the last DrupalCon Dave Reid had a session on what decisions you can make now on your current or new Drupal 7 sites to make transitioning to Drupal 8 easier:

  • What field modules can I use that work the same as Drupal 8?
  • What WYSIWYG editor should I use?
  • How can I start preparing to migrate my existing Drupal site to Drupal 8?
  • What kinds of modules can I use so I don't have to retrain my editors and administrators when we move to Drupal 8?
  • I'll also cover some basic concepts for those of you writing Drupal 7 modules that you can do right now to better prepare yourself for writing modules in Drupal 8.