Easy Cache
Component type
Categories
Maintenance status
Development status
Component created
Component changed
Makes it easy to cache any callback's result using an autogenerated cache key.
Usage:
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 adds ability for Pathauto to translate aliases into English using Yandex Translate API, which is relatively free by this moment (limited by 10 000 000 translated symbols per month). This module may improve your SEO, making your local language URLs not just transliterated but qualitatively translated into English.
After exceeding service daily or monthly limits the module will fall translating back to transliteration and send a notification for site administrator.
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:
Ever wanted a page that displays all its links to open in a new window? Like a page embedded in an iframe?
To do this
You may also like Panels HTTP Response Header Pane.
Do you have a site that provides multiple ways to get to the same content (for example, each piece of content is associated with several different taxonomy terms)? What if you need to provide a way for the site visitor to go back the way they came?
Follow Me provides an API for keeping track of what views, taxonomy terms, etc.
a user has viewed leading up to viewing the current page.
Consider these e-commerce use cases:
This Commere Stock contrib module uses hook_base_info_alter to add three base fields to any commerce_product_variation:
- stock_field (a commerce_field_stock) which is managed by the commerce stock api.
- allow_no_stock_sale (boolean)
- no_stock_message (textfield)
The module then overrides the default commerce_stock StockAvailablityManager to consult the above fields to see if it has stock, and if not, is it still allowed to make available the requested amount of stock.