'Access Denied' to nodes using Workflow modules

audrey - March 27, 2008 - 14:24

Hi --

I installed the workflow module, configured a new content type and all the workflow states to go with it. I added a new role for users with permissions to change the workflow state on that content type.

The problem I'm having is that only the author of each node and administrator can access any node of that content type. All anonymous users, and authenticated users (including members of the role with edit permissions) get 'access denied' when attempting to view the nodes.

I have checked and re-checked the workflow access permissions... I retained the default: anonymous and authenticated users SHOULD have viewing access to that content type regardless of the node's workflow state, and members of that special role are given edit permissions on that content type for every workflow state. I even explicitly added viewing access for members of that special role, but still they cannot view nodes that they did not create. BTW: there are no taxonomy categories involved with this content type, so it's not a permission problem propagated from that.

Any ideas on why I'm getting 'access denied' unless the user created the node (or is admin)???

I am experiencing this as

xamount - November 22, 2008 - 20:24

I am experiencing this as well. I applied the patch from #296086: workflow_access permissions not aligned with roles but I still experience the same problems.....can't figure this one out. Any help appreciated.

I am using Drupal 5.10
Actions 5.x-2.6
Triggerunlock 6.x-1.0
Workflow 5.x-2.3

Sometime i found out thats

xamount - November 23, 2008 - 01:44

Something i found out thats interesting:

I have nodes set to NOT be published upon creation. So the state will be draft. Now another user who should have permissions to view nodes in the state of draft should be able to view this node (as specified by workflow_access.module). But they can't, they get access denied.

If I give that role "administer nodes" permissions, then they can view the node, but now they are able to make the nodes published which is not what i want.

So it seems that workflow_access.module does not handle this drupal published state very well (if at all)....or maybe its something to do with workflow_access.module and the administer nodes permissions.

You might want to read and

ckng - November 24, 2008 - 02:03

You might want to read and understand carefully how node access works..
http://zivtech.com/blog/drupal-node-access-explained-0

Most likely you did something wrong.

CK Ng | myFineJob.com
consultation • web design & development • content development • site domain, hosting & maintenance • software design & development

 
 

Drupal is a registered trademark of Dries Buytaert.