Blair Wadman

Primary tabs

Articles from Blair Wadman

This post is part of a series of posts on making changes in Drupal programmatically rather than in the Drupal interface.

Keeping your Drupal site up to date has always been of critical importance to ensure it remains secure.

There is a lot of talk in the Drupal community and media about the Drupal security vulnerability that was fixed in the Oct 15th update (7.32). If you have missed the details, here is a summary:

Recently one of my clients had a problem with a large portion of transactional email never being seen. The emails were being directed to the recipients' spam folders and were generally being over-looked.

We all know the importance of backing up the database for each Drupal site we build and maintain. But it is not uncommon for this to be put on the back burner and never actually implemented.

Drupalcon Amsterdam kicks off on today and it looks like it is going to be a great event, especially with Drupal 8 Beta about to be released! Sadly, we can't all be there. But that doesn't mean we have to miss out entirely.

The Drupal Features module covers a lot of our needs with automating the deployment of database settings for Drupal 7.

A few weeks ago I was ready to turn off the comments on my blog. Despite having Mollom running, I was left with a non trivial amount of spam comments to manually deal with each day. It felt like a waste of my time.

One of the key features of a Drupal module is an admin interface. An admin interface enables you to make a module's settings configurable by a site editor or administrator so they can change them on the fly.

The Features module is a vital tool in the Drupal developers and site builders arsenal.

Pages