| 1 |
// $Id$
|
| 2 |
|
| 3 |
Module: Field Actions
|
| 4 |
Requires: Actions module and CCK
|
| 5 |
|
| 6 |
OVERVIEW:
|
| 7 |
|
| 8 |
The Field Actions module combines the power of Drupal actions with the data in
|
| 9 |
CCK nodes to create new ways of working with your nodes in Drupal. This module
|
| 10 |
enables action enabled modules (such as workflow.module) to reach into your
|
| 11 |
nodes, pull out information, and use it appropriately. This leads to more reuse
|
| 12 |
of data throughout your site, and easier creation of behavior for
|
| 13 |
non-programmers and programmers alike.
|
| 14 |
|
| 15 |
INSTALLATION:
|
| 16 |
|
| 17 |
Download and install the actions and CCK modules. You may also wish to install
|
| 18 |
the workflow module, as actions have no user interface of their own.
|
| 19 |
|
| 20 |
http://drupal.org/project/actions
|
| 21 |
http://drupal.org/project/cck
|
| 22 |
http://drupal.org/project/workflow
|
| 23 |
|
| 24 |
Enable these modules on your modules adminstration page, and then enable this
|
| 25 |
module.
|
| 26 |
|
| 27 |
CURRENT ACTIONS:
|
| 28 |
|
| 29 |
User Reference Actions:
|
| 30 |
- Send an email to a user reference field
|
| 31 |
- Assign ownership of a node to a user reference field
|
| 32 |
|
| 33 |
USAGE:
|
| 34 |
|
| 35 |
Create a node type that uses any of the fields listed in the Current Actions
|
| 36 |
section of this file.
|
| 37 |
|
| 38 |
Visit yousite.com/admin/actions and select the appropriate action from the drop
|
| 39 |
down list. Choose the right field from your list of options, complete the form,
|
| 40 |
and save your action. It is now ready to use in a workflow or other action
|
| 41 |
enable module.
|
| 42 |
|
| 43 |
TO DO:
|
| 44 |
|
| 45 |
1. Add actions for other CCK fields. Some plans include:
|
| 46 |
- Apply action to node referenced by field - apply an action to every node
|
| 47 |
listed in a node reference field. Additionally, do the inverse, apply action to
|
| 48 |
every node that references a the acted on node from a given field.
|
| 49 |
- GET or POST data from/to a given web url field
|
| 50 |
- Combine fields to work in tandem
|
| 51 |
|
| 52 |
2. Define a field that contains a UI for invoking actions on certain events
|
| 53 |
(i.e. submit/save, new revision, cron interval, etc).
|