trigger.module
Version 1.13.2.3 (checked in on 2009/06/08 at 16:34:57 by goba)
Enables functions to be stored and executed at a later time when triggered by other modules or by one of Drupal's core API hooks.
Functions
| Name | Description |
|---|---|
| trigger_access_check | Access callback for menu system. |
| trigger_actions_delete | Implementation of hook_actions_delete(). |
| trigger_comment | Implementation of hook_comment(). |
| trigger_cron | Implementation of hook_cron(). |
| trigger_forms | Implementation of hook_forms(). We reuse code by using the same assignment form definition for each node-op combination. |
| trigger_help | Implementation of hook_help(). |
| trigger_menu | Implementation of hook_menu(). |
| trigger_nodeapi | Implementation of hook_nodeapi(). |
| trigger_options | Often we generate a select field of all actions. This function generates the options for that select. |
| trigger_taxonomy | Implementation of hook_taxonomy(). |
| trigger_theme | Implementation of hook_theme(). |
| trigger_user | Implementation of hook_user(). |
| _trigger_get_hook_aids | Get the aids of actions to be executed for a hook-op combination. |
| _trigger_normalize_comment_context | When an action is called in a context that does not match its type, the object that the action expects must be retrieved. For example, when an action that works on nodes is called during the comment hook, the node object is not available since the... |
| _trigger_normalize_node_context | When an action is called in a context that does not match its type, the object that the action expects must be retrieved. For example, when an action that works on users is called during the node hook, the user object is not available since the node... |
| _trigger_normalize_user_context | When an action is called in a context that does not match its type, the object that the action expects must be retrieved. For example, when an action that works on nodes is called during the user hook, the node object is not available since the user... |