Extensions
Component type
Categories
Maintenance status
Development status
Downloads
Component created
Component changed
Extensions is an alternative method of pluggable object creation (ala Chaos Tools plugins).
The key features of Extensions are:
Extensions is an alternative method of pluggable object creation (ala Chaos Tools plugins).
The key features of Extensions are:
Integrates with the twitter API based upon the flux Services integration.
This is an integration module, so it does not expose any end-user functionality. It integrates Drupal with the twitter API by providing remote entities and integration with the Rules module.
Integrates with the facebook API based upon the flux Services integration.
This is an integration module, so it does not expose any end-user functionality. It integrates Drupal with the facebook API by providing remote entities and integration with the Rules module.
Handle duplicate entities well! Scan for duplicate entities, and merge them. Includes integration with Relations and Rules.
Define which fields should be compared (e.g. title and date) on each entity. If they match, entity is flagged as duplicate. Merging UI lets you choose a master entity and merge the rest in.
This module provides a cache class exposing hooks allowing other code to intercept calls to the caching layer. by implementing those hooks it is possible to alter expiry before an object is saved to the database or to prevent a cache flush under some condition.
In order to expose the cache object hooks only for the cache_form bin, put the following lines into your settings.php:
Varnish Tagged Cache Invalidation
Tamper is a generic API for transforming data. For now, just see Feeds Tamper.
The Field Widget Storage API module is a storage engine that can be used by any field widget that needs to save extra configurations alongside a field. Developers are able to leverage the modules API so they don't have to worry about implementing CRUD functionality for their field widget.
In a multi-environment setup (e.g. prod, test, dev, local) there are some modules that you'd like to always be enabled or disabled on certain environments. Each time you sync a database down though you have to re-enable/disable the same modules. Worse, you get lazy and keep development modules enabled on production.
This is a development helper module that enables your developers to see: