// Render permission overview:
$options = array();
foreach (module_list(FALSE, FALSE, TRUE) as $module) {
  if ($permissions = module_invoke($module, 'permission')) {
    // List only the modules that have permissions.
    dsm($module);
    dsm($permissions);
  }
}

This is a helper function when order is locked, validation fails and status cant be changes.

$order = commerce_order_load('219215');
commerce_order_status_update($order, 'pending', FALSE, FALSE);
commerce_order_save($order);

This is a helper function when order is locked, validation fails and status cant be changes.

$order = commerce_order_load('219215');
commerce_order_status_update($order, 'pending', FALSE, FALSE);
commerce_order_save($order);

watchdog('debug',kprint_r($var, TRUE, NULL));

I am trying to integrate pay with amazon to drupal site and had a hello of a time, trying to figure out how to do that. They use namespaces and that is not something so common in drupal 7. So to understand it better, check out this video and this blog post

There is interesting discusion about this here
https://www.drupal.org/node/671574#comment-6466782

Drupal has a very simple, yet powerful (low level) caching system. It provides 3 functions that should please all you caching needs: cache_get, cache_set and cache_clear_all. The first two are pretty straight forward to use, but the third one might take some time to wrap your head around.

So to cut it short, just write this in your code, probably devel/php, change the filed name and you will have unlock a filed (probably commerce_price field).

So importing data from WP is not so hard, you can do it in different ways, mapping data as you need. But what to do about passwords. they are encrypted, WP uses "one-way encryption" and you will need hacker to know what is in them. There are 2 methods.

1. Copy paste

One of those things. We have spent 4 hours, 2 persons combined hunting down this problem. Google GTM code, which we for specific reason enabled on node add forms, broke all ajax forms and made crayze problem of opening new browser window instead of editing the node reference field with inline entity form. The same thing happened also on image upload widget.