Drupal Services User.register resource JSON format oddity

This is mostly a note to myself. When calling the user.register method for the Services module, the JSON data format is a little wonky:

{ "mail":"[email protected]", "postal_code":"21401", "account":{ "name":"username", "pass":"password", "mail":"[email protected]" }, "field_name":{ "und":[ { "family":"Grasmick", "given":"Matthew" } ] } }

Introducing the Unsubscribe module

I recently began sending out mass emails via Drupal, and I was surprised to find that no universal solution existed for providing an "unsubscribe" link on Drupal emails. Sure, you can use Subscriptions to manage actual subscriptions to content, or Notifications for activity notification preferences, but what if you just want to unsubscribe from email communication in general? What if your Drupal admins periodically send out mass emails manually, and you'd like to unsubscribe from even those?

Programmatically render a Drupal view with exposed filters, arguments, etc.

Embedding a view programmatically is not too difficult, but what about passing it a value for an exposed filter? This snippet gives a simple example of how to modify the View object in a more meaningful way before rendering it.

$name = 'my_view';
$display = 'block_1';
$view = views_get_view($name);

If you'd like to pass in exposed filter values, define these properties before calling $view->preview():

Demystifying Views API - A developer's guide to integrating with Views

Learning to use the Views module from the front end of Drupal is a daunting task, but you can rest assured that many others struggle along with you. There are many tutorials and screencasts dedicated the the subject. Tackling the Views API from the backend, however, is a bit more of a challenge. It's not easy to document the behemoth that is Views, and hence, the documentation is limited.