Giant Robot

"Doesn't Play Nicely" is a presentation given at DrupalSouth Wellington 2010.

Providing technical support to Drupal developers and implementors, there are plenty of examples of module conflicts you get to see. I decided to throw together a handful of examples in order to stimulate some reflection amongst the developers in the audience could help avoid such conflicts in the future.

This is a pre-release of a Drupal 5 module which allows you to record JavaScript errors from visitors either to the Drupal log, or (if you're really keen to hear about it!) have immediate notifications sent by email.

On the Paper Fish website, we use jCarousel to display a carousel of similar products. It works really well, but for some Safari users it gave a strange error, which was proving hard to reproduce on our test machines. In order to leverage the users visiting the site in order to test the system more completely, we produced this module.

We had a need for a Drupal module which would add a customisable user registration question - this is to allow the owner of a book to register for additional features on the associated website.

In order to make this as widely useful as possible, we've implemented it as a CAPTCHA plugin, so that any Drupal form can take advantage of the functionality. You'll need to have the

This is an early release of the code - it's working for us, but we welcome any feedback from the community.

Geoff Butterfield and Angie Byron gave a tech talk with an overview of Drupal, who uses it, and how it works, and then specifics about how it's implemented in the site Edutopia.org.

Angie introduces Drupal, while Geoff gives details about how extensive use of Taxonomy, Views, and CCK helped make the website possible.