Allows users to create block instances of predefined block types registered by other modules.
Features
Difference to core blocks:
Modules register block "types".
Administrators can spawn new instances of a block type.
Block instances are entities.
Unless a block type opts out, Block API takes over the storage of configuration settings per block instance.
Major ideas and parts for the block instance handling have been based and borrowed from JohnAlbin's excellent Menu block module.
An example API implementation is available in a hidden testing module, which provides the equivalent of custom blocks in core; i.e., a simple title and HTML body.
Block API itself provides no block types on its own.
MIME Router handles mapping incoming attachments via mailhandler and routing them to the appropriate CCK filefield(s). MIME Router relies on the incoming media MIME type to determine the appropriate filefield to route incoming attachments to. There is no configuration necessary as MIME router relies on the configured CCK filefields allowed file types. MIME router iterates over the available filefields configured for use with mailhandler and drops incoming attachments into the first filefield that allows files of the given type.
This module allows you to insert tokens into a textarea. It supports both plain text and wysiwyg textareas. The format used for the insert is compatible with Token Filter.
This module contains three modules:
Token Insert UI: Allows you to select which tokens are available for the insert, by default all tokens are shown. This module doesn't have to be enabled to use the others.
Token Insert (text): Add a fieldset under each textarea, works for both plain text fields and wysiwyg fields.
Token Insert (wysiwyg): Adds an extra button to wysiwyg editors and opens a popup to select the token to insert.