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.
This is a bit late on the #drupalgeddon // #drupslsa05 post, but the need to update is just too alarming to go unmentioned. Like this tweet from @outlandishjosh
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.
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 Vagrant, 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.
Drupal is great at a lot of things, one of those being the feeling of your head banging against the wall. Drupal can lead to some headaches when things just do not work right. Troubleshooting and debugging in Drupal doesn't have to be difficult, however. Yet, for some reason, every article I've ever found goes in too deep. I presented this at my user group Drupal 262 as a "back to basics" debugging and troubleshooting.