To help make this module have a wider user adoption, I think somehow having the ability of (re)using action.module or Drupal 6 actions should be incorporated.

Not that the way of workflow_ng actions should be scrapped, but someway to extend the means that this is done would be very useful.

A few sites I know or work on would be interested in this module, but we already have many actions setup, some are custom actions. So to rewrite all of these to fit into a new API would be a drap. I would imagine many others dev will also come so such a crossroad, and choose not to do the extra work.

-Greg

Comments

fago’s picture

fago
Primary language German
Location Vienna
commented

I agree that this makes sense - however drupal 5 actions are a bit different. Perhaps it would be doable with a legacy action, which can configure drupal 5 actions.
Supporting drupal 6 actions will be easier, as parts are quite the same.

Gman’s picture

Gman commented

Great to here about the Drupal 6 flexibility. That is probably a good place for people switch over to this system if they were using another system. I know my boss will allow my rework/refactoring when we move sites to D6.

fago’s picture

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

This feature will be available with 6.x, so I set it to postponed (for 5.x)

fago’s picture

fago
Primary language German
Location Vienna
commented
Title: Allow Actions.module or Drupal 6 actions to work » Allow Drupal 6 actions to work
mitchell’s picture

mitchell commented
Component: Code » Wng API
Status: Postponed » Fixed

Rules supports the latest actions implementation.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.