Using Features Override to manage changes to a distribution

The module has become a de facto tool in configuration management in Drupal 7. In fact, most Drupal distributions now utilize Features to export configuration and handle updates to the configuration. There is one pitfall - Features was  meant to be a way to export a feature set. Features takes a set of configurations and its job is to ensure those are in place. That means customizations to defaults are at risk of preventing incoming changes or loss when updating.

Drupal Commerce, Deconstructed

Recently I presented at the Drupal 414 user group in Milwaukee on "Drupal Commerce, Deconstructed" to break down what makes Drupal Commerce and better explain some of its inner workings. The goal isn't to blow the minds of advanced users, but to sell it to all on its flexibility and help users understand why certain things are how they are. I've also submitted it as a session to .

Fixing "UpdaterException: Unable to determine the type of the source directory"

I don't use the built in update functionality provided by the Update module for updating code. I like to use it for reminders and push back statistics of modules used for However, someone people do use it. Sometimes this piece of functionality can fail and throw an interesting message which doesn't seem to have many answers despite the best Google-fu.

Role Provisioner: Drupal 7 role and permission management

If there's one thing we've all grown to encounter in Drupal it has, and probably will always be, configuration management. Drupal 8 is looking to solve a lot of that. However a lot of us don't live in the Drupal 8 world and can't sit and wait for that "magical" day. Features gives us a lot of functionality, but after a certain point Features either breaks down or becomes too cumbersome to manage.