I propose we add the workflow_access.module to our package for 5.0. You can find a 4.7 version of workflow_access at http://cvs.drupal.org/viewcvs/drupal/contributions/modules/na_arbitrator/. A 5.0 version of that module would no longer depend on na_arbitrator since core is now flexible enough.

I might find some time to update that module if I get some consensus here that we actually will use it.

Comments

moshe weitzman’s picture

moshe weitzman commented

anyone have an opinion on the merit of this?

jvandyk’s picture

jvandyk commented

+1 for taking workflow_access under the wing of workflow. You need workflow to use it, right? So it should be module in the workflow distribution, dependent on workflow.

Lowell’s picture

Lowell commented

Am using in 4.7 and learning how to add custom actions. I think it is a valuable module and if this means it is more integrated into Drupal then I am all for it.

Lowell

mfredrickson’s picture

mfredrickson commented
Status: Active » Postponed

I agree that this is the appropriate thing to do. I'm postponing this issue until the 5.0 branch is created.

xjm’s picture

xjm
she/her
Primary language English
commented

You have my vote. This would be an extremely useful feature for the workflow module. (Work on the 4.7 workflow_access module is low since it's a "demo module," and there probably won't be a 5.0 version since na_arbitrator is purportedly integrated into the core for 5.0.)

moshe weitzman’s picture

moshe weitzman commented
Status: Postponed » Active
zeitenflug’s picture

zeitenflug commented

+1. Great idea. Great need for it.

mfredrickson’s picture

mfredrickson commented
Status: Active » Fixed

Added.
http://drupal.org/node/138170

killes@www.drop.org’s picture

killes@www.drop.org commented
Status: Fixed » Closed (fixed)