Drupal Commerce has the best implementation for handling virtual products sales as if in a real life store, in my opinion. Each product has a product display (or container) which houses each individual product, a variation per se, ( ex: shirt Z size small, shirt Z size medium) which provides better stock management and a streamlined business process if you do have a physical store and virtual store. There's just one major caveat: each product variation has to your product data attached, not the product display. So a t-shirt with 6 sizes is actually 6 products.
I just pushed Facebook Album 2.0.1 to WordPress.org. This should fix issues with getting the album ID for personal albums, along with the Show Album Title option not working, amongst a few other bug fixes.
I have just pushed out version 2.0 for the Facebook Album WordPress plugin! Go on and get it, or use your WordPress's plugin updater to get the latest version. Need help?
I've been hard at work in the labs revamping the Facebook Album plugin for WordPress. Very soon you will be able to use a Facebook application to authenticate with the Facebook API.
Drupal uses a cron to take care of clean up tasks, as well as utilizing certain features. By default Drupal executes its cron run every three hours based on a user visit. This causes the cron to be executed over HTTP. Depending on the generally it can be more efficient to execute your Drupal cron directly through PHP command line on the server side versus HTTP.
One thing that I has always bothered about WordPress widgets is the lack of ability to define custom widget CSS classes for each widget - it is kind of ugly using the stock widget IDs when you have four text widgets. I've been working on a plugin to extend widget functionality to match features found in Drupal's blocks. I just posted a GitHub gist quickly highlighting the WordPress filter hook.
I finally got my first codepen.io account, and created some CSS Facebook Chat heads. You can check out the pen, and play around with it.
I migrate a lot of WordPress installs from a localhost to the beta server and then to production. It's easy enough to update the URLs in _options and guids in _posts, but the one thing that irritated the hell out of me was the rewrite rules. WordPress caches the rewrite rules within _options; if you've migrated a WordPress you'll notice links are broken even though .htaccess is fine. Simply find "rewrite_rules" in _options table and clear out it's value - badda bing.