Managing your Drupal platform with Drush

One of the benefits to using Drupal is harnessing the command line tool Drush. If you don’t know about Drush, I advise heading over the the  and also . Drush is powerful because its commands allow you to simplify your workflow - from clearing caches to migrating databases across environments. One of the best features, in my opinion, is the make command. Using Drush you can build Drupal with specific libraries and modules from a makefile. To make it even more awesome you can patch these projects through the makefile.


A recent project of mine has been for the Drupal community. The name speaks for itself - it provides a way for contributors to work on project issues queues through a kanban board. This app has two purposes: visualize the project issue queues in a useful fashion, and provide an experiment that tries to fully utilize APIs.

Drupal Issue Tracker, Chrome App

Yesterday I released a Chrome application to provide a simple method for keeping track of project issues. Take a issue number (the node ID) and add it to the app. It will then utilize's REST APIs and keep track of the issue. This allows you to keep a collection of important issues and periodically check their status. I've put the Chrome packaged app source up on GitHub:

But, why?!

Programmatically change the "Add to Cart" line item type

Drupal Commerce has a very interesting "Add to Cart" form. The add to cart form is a field formatter for the product reference field (or even entityreference field.) In a general sense, a node has a product reference field using the "Add to Cart" formatter. What makes it more unique is that this form exposes certain fields from the product entities, but also the line item type being used. Specific fields on products can be exposed as attributes, things you pick to make your purchase. Exposed line item fields allow you to get customer input values on that specific item added to the cart.