down arrowMenu

UNI Webtools: Resources for Web Developers


Mediacurrent: Highlights From DrupalCon Los Angeles

Posted on Friday, May 22nd, 2015 by drupalroot

DrupalCon Los Angeles Recap

Last week, was in sunny Los Angeles for DrupalCon 2015. Though many were seasoned veterans, it was my first time at a Con. It was a whirlwind of team building, a magical Prenote, great one-on-one coversations and plenty of Drupal talk. Needless to say, I'm still recovering! But if one thing is certain, our team had a wonderful time. Here are some of their takeaways:

Paul Booker: Creating an action to update the prices of your commerce products

Posted on Friday, May 22nd, 2015 by drupalroot
 * Implements hook_action_info().

function mymodule_action_info() {
  return array(
    'mymodule_update_products' => array(
      'type' => 'entity',
      'label' => t('Update products by 2%'),
      'configurable' => FALSE, 
      'triggers' => array('any'),
      'pass rows' => TRUE,
function mymodule_update_products(&$entity, $context) {	
  $product_id = $entity->product_id; 
  $price = $entity->commerce_price[LANGUAGE_NONE][0]['amount'];
  $updated_price = 1.02 * $price;
  $affected_rows = db_update('field_data_commerce_price')
    ->fields(array('commerce_price_amount' => $updated_price))
    ->condition('entity_id', $product_id)

Gábor Hojtsy: New easy ways to explore Drupal 8's multilingual capabilities

Posted on Friday, May 22nd, 2015 by drupalroot

The Drupal 8 multilingual team is really great in spreading know-how on the new things in the upcoming version, so we had our session (1h) and workshop (2h) recordings published and widely available. While we of course love our baby and can talk all day about it, who has hours when they just want to explore what is coming up? We just addressed that this week with the following.

Julian Granger-Bevan: A Git Workflow for Drupal Modules

Posted on Friday, May 22nd, 2015 by drupalroot

Years ago now, the Drupal community adopted Git as a version control system to replace CVS. That move has helped development since the distributed nature of Git allows better tracking of work privately before uploading a patch to

Sandbox repositories allow contributors to clone an existing project to work on independently (therefore not needing permissions for the canonical repository), but there is currently no way that I know of to request that those changes are pulled back, facilitate a review of changes and then merge the changes in (a pull request).

Hopefully that functionality is on the way!

But as a community the challenge is not just the development on, collaboration with GitHub, or whatever form the technical change takes. Alongside those changes, we need the workflows that will help us better manage multiple versions, allow fast bug fixes whilst features are being tested, and provide for reviews without alienating developers. And the technical element goes hand in hand with the workflow.

As an example, for the Drupal PM module, we recently debated how to set up Git branches to allow more flexibility than the traditional "single line of code" inheritted from CVS.


Subscribe to RSS - blogs