Dries has stated his desire to have actions in core.
John VanDyk has stated his basic roadmap for actions.
This group is meant to be a working group where discussions about actions architecture take place.
Actions Email
I have this requirement that needed the site moderator (not admin) to manage email templates.
The questions are :
- Can I create a custom admin settings form to save the templates to specific Action?
- If can, is there any step by step on doing this?
BTW, I'm not that good in creating custom modules, but I have basic knowledge on that.
Thanks a million in advance.
Update : Sorry this is for Drupal 6
Read more
Drupal 6: Send customized emails to multiple addresses from fields within multiple field groups
I have a multi-step form that is a job application.
On one step the applicant enters information for professional references, and on another, character references. They may add multiple references (field groups) on each page. The field groups for both types of reference include an email field, and a hidden "email sent" field.
At the end of the form, when the applicant submits the form, I wish to send customized emails to each of the references, and populate the "email sent" field with "yes".
Read moreAction needed for the "After/before deleting a post" trigger
I have a node type A (parent) and a node type B (child). B-nodes have a mandatory CCK nodereference field that points to a parent A-node.
A1
|-B1
|-B2
|-B3
Currently it is possible to delete the parent A-node and all child B-nodes immediately become inconsistent (a mandatory nodereference field points to an non-existing parent). CCK does not address this flaw and I need a workaround. Reading through the documentation I found out that it might be possible to create a custom action (in D6) that will delete all child nodes when (before) the parent is deleted.
Read more
A session about rules at the drupalcon?
I've created a session proposal for the drupalcon :)
-> see http://szeged2008.drupalcon.org/program/sessions/rules-new-opportunities...
I'd also talk about the differences to the core actions and trigger module. Look at the session description for more infos.
Hopefully the session will be selected and I'll see you there.. :)
Actions is in core
Wake up group members. Actions got into core and noone here said anything. Whats next for our intrepid module. Conditionals? How to do that?
Read more
Actions Bonus Pack
While we wait for modules to implement actions, is there room for an "actions_bonus" style module?
Read moreWorkflow-ng 1.0 released!
Finally the first stable release of workflow-ng is out!
The module is already stable for a long time and all important features are implemented, so I decided it's time to release. So I'm happy to have a stable 1.0 release out of the door close before the drupalcon in barcelona. If you are going to barcelona, don't miss the session about workflow-ng.
Links:
project page
documentation
Workflow-ng 5.x-1.0 beta1 released!
I'm happy to announce the 1.0 beta1 release of workflow-ng.
Workflow-ng allows one to customize drupal's built in workflows in a very flexible way.
In short, it's a rule-based event driven action evaluation system. Read the introduction to see how it works.
It is useful for
- sending customized mails notifying your users about important changes
- building flexible content publishing workflows
- creating custom redirections
- and a lot more....
Actions accepted into core
Actions will be part of core Drupal in next version. Nice work, John.
Read more
Views and bulk actions
One of the useful Web patterns I've been noticing has to do with item lists and bulk actions. Given a list of items, add a checkbox in front of each item, and let the user select an action to be executed on the checked selection. Specifically, I've seen it in phpMyAdmin, Mantis, and Google Mail.
Read moreWorkflow-ng API ready...
After some hard work, the workflow-ng API is ready.
It features
- actions, which may be configurable
- conditions, which may also be configurable
- support for multiple arguments, for actions as well as for conditions
- condition evaluation with logical operations like OR, AND and NOR
- events, for which conditions and actions can be configured. They may be contributed by modules.
- dynamic loading of needed arguments
- ordered conditions and actions - they are evaluated like they are ordered
- form API style configuration and processing of conditions and actions
So workflow-ng works event based. (And no, I'm not talking of calendars ;)
E.g. workflow-ng defines some basic events for drupal core, like 'node update, 'node insert', 'user update' and so on. So this are the events you can react on by defining conditions and actions for them.
What makes workflow-ng powerful is, is it's flexible handling of arguments. Each of these events has to define a list of available arguments. Then any conditions and actions, that can work with these arguments, can be configured for this event. So an action can be used in any situation, where the suitable arguments are available. There is no need for the action, to be coded aware of every event.. :)
As modules may define further events, this enables module authors, to easily allow site administrators to customize the behavior by just defining some further events.
Read more at http://more.zites.net/workflow-ng-api-ready
Read moreFeedback on HEAD actions
I did a whole review of actions module UI and then lost it. damn macbook. here is short version, from memory
BUGS
- I added a make sticky+save node actions upon comment insertion. i expected the source node to become sticky but it didn't. sticky action assignment did work as expected on the node tab.
- I got some error when creating a 'display message' action. I think a missing system_foo_validate function.
MISC - ASSIGN ACTION
- assign action should be default tab
Actions? Callbacks?
I went through the code. I kind of understand it, now. You know I like the idea, and I think we should have this facility in core. This is more a discussion for the future of where and how is this going.
Ultimately, with this 'structured array' thing getting everywhere, I think actions and #callback should end being the same. The only difference should be action_info, that is actions being visible to the system, and potentially wired up via an admin UI.
Read morefiring actions on events
continuing the discussion from http://lists.drupal.org/pipermail/development/2007-May/023657.html
code: http://cvs.drupal.org/viewcvs/drupal/contributions/sandbox/fago/workflow...
The next steps would be:
* let actions define which arguments they need
* Collect assigned actions for events
* Map the arguments appropriately
Mutating actions
Actions currently are written the following way. We use a naming convention of a function starting with 'action_' to denote an action. Within the action we have various ops, as follows:
<?php
/**
* Implementation of a Drupal action.
*/
function action_block_user($op, $context = array(), &$object) {
switch ($op) {
case 'do':
global $user;
// block user here...
break;
case 'metadata':
return array(
'description' => t('Block current user'),
'type' => 'User',
'batchable' => TRUE,
