Adds a class to ajax-ing elements and body and disables the default throbber.
All ajax loading can then be styled in CSS using classes:
body.ajax-waiting
body.ajax-complete
input[type="submit"].ajax-class-trigger
Provides a themeable template for an order summary (line items, subtotals and order total), and tokens [commerce-order:order-summary] & [commerce-order:order-summary-plain] (using separate templates for HTML and plain text version, eg. for use in plain-text email).
Want simple shipping without rules? This module creates a shipping product type and line item type. Store managers can create a shipping product (or products) and developers can add it to an order using their own logic.
Also provides token [commerce-order:shipping-lite] which gives the first shipping product on an order (if any).
Makes it easy to cache any callback's result using an autogenerated cache key.
Usage:
Provides a Form API element type 'entity_field' for getting / setting a field from an entity.
eg. given a page $node, with field 'field_foo':
$form['title'] = array(
'#type' => 'entity_field',
'#settings' => array(
'field_names' => array('field_foo'),
'entity' => $node,
),
);will attach to $form the rendered field widget for the field_foo instance attached to page nodes.
Additionally, the field can be rendered with an empty value to create an entity on submit:
An alternative approach to Pathauto - using the pathauto alias field as a slug - ie. can't contain forward slashes. Any entered value replaces entity label tokens (eg. [node:title]) in any pathauto patterns.
This can be used to eg. enforce hierarchical pathauto patterns using menu path tokens, eg.:
[node:menu-link:parents:join-path]/[node:title]
This is an implementation of the Hungarian GLS shipping method for Drupal Commerce shops.
sandbox
This module track logs of specific events that you'd like to review. The events performed by the users (using the forms) are saved in the database and can be viewed on the page admin/reports/events-track. You could use this to track the number of times the CUD(Create, Update & Delete) operations performed by specific users.
Currently, the following sub modules of Events Log Track are supported:
This module contains extra layouts for the Layouts module, ans usable e.g. for Display Suite and Panels.
Currently it contains
The content-first layout has the following properties: