This module allows a default value for a view argument to be specified based on a piece of contextual data set through the Context module's context_set function. When configuring the default argument, you specify the context namespace and the attribute name, and the value is pulled automatically. This is particularly useful for getting information to Views blocks. This is far less hackish than specifying path arguments via arg().
Example use case
Let's say we have a Views block. It's supposed to list all of the nodes that are nodereferenced to whatever node is specified in the argument to the view like so:
nid:23
|_____nid:45
|_____nid:29
|_____nid:35
etc.
Because there's no good way to send arguments to blocks, the traditional approach is to set the View's "Default argument" parameter to PHP code containing:
return arg(1);
...or something similar. It is hackish and terrible to rely on the URL for the current nid -- that approach fails to keep the control hierarchy intact (node/xxx invokes a node controller, and if views is invoked somewhere in that stack, it should not be able to jump all the way up to the node controller to retrieve its arguments -- the node or page controller should supply those arguments).
Hover preview Javascript effect for the ImageCache module. Allows for hover FROM any ImageCache preset TO any other ImageCache preset. Supports views and standard theme-layer output options.
Adds support for multi-level drop down menus via the Superfish jQuery plugin. Compatible with keyboard navigation, screen readers, small screens and touch devices.
This module integrates with the API of Chargify's recurring billing system. This module is an API wrapper for this library only, and doesn't actually "do" anything unless you implement the API in your own module. It's built according to the Chargify API version 1.
Installation
Install the module as usual into your Drupal site.
Enter the Domain and API key for your Chargify account on the configuration page (/admin/config/services/chargify).
Make sure you set the proper permissions ("access chargify").
Usage
The general concept is to first get a controller for the resource (product, customer, etc.) that
you want to interact with and then use the functions available.
For example to get a listing of all products in the system: