Workflow-NG defines its own API for actions, which is different from the one in action.module. However, right now there are plenty of contribs based on the actions module and it would be great to expose them via Workflow-NG.

As far as I understand, the action APIs in Workflow NG and the standalone module are functionaly very similar, even though they have different signatures. This brings up a question of whether it might be possible to create a compatibility wrapper to expose standalone actions via Workflow-NG. This would enable access to many contrib action modules.

On the flip side I wonder if Workflow-NG and actions module might conflict. I see actions in 6.x (http://drupal.org/node/172152) define an effectively conflicting hook (action_info). Would there be any caveats in 5.x?

Right now backup_migrate.module seems to implement both action types and could serve as an example of the problem.

Comments

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Postponed

In 5.x I won't do it as there are too much differences, in 6.x the similarity is no coincidence, workflow-ng will support executing d6 actions.

dkruglyak’s picture

dkruglyak commented

OK, thanks for clarifying. Final question for 5.x, is there any downside to having both modules on at the same time? Any conflicts?

fago’s picture

fago
Primary language German
Location Vienna
commented

no.

dkruglyak’s picture

dkruglyak commented
Version: 5.x-1.x-dev » 5.x-2.x-dev

Marking for 2.x