Drupal Issue Tracker, Chrome App

Yesterday I released a Chrome application to provide a simple method for keeping track of Drupal.org project issues. Take a Drupal.org issue number (the node ID) and add it to the app. It will then utilize Drupal.org'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: https://github.com/mglaman/drupalorg-issue-tracker

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.

Facebook Albums 3.0!

It's been a long time, but I've decided to work out a new version of Facebook Albums. This will bring it up to speed with any Facebook API changes and WordPress. The plugin hasn't had any real work done since 3.5 came out. The main goal is to provide a better class at handling API interaction and hopefully more functionality.

MySQL Workbench + Vagrant

I've been using Vagrant at work for a few months now - and I got into it specifically for mimicking our product environment. If you don't know about , I highly suggest you check it out. I recently purchased an iMac and I'm utilizing Vagrant VMs for all development. That means I have a few select environments and my machine is bogged down with extra services or dependency issues.