I am using workflow, revisioning and module grants for a fine-grained workflow implementation.

I am running into a problem where a role that is defined to have edit capabilities for a node is not being permitted to do the edit. I looked at the workflow access table, and it seems that the permissions are correct.

After uncommenting some debug lines in module grants -When I view Accessible Content menu item (module_grants), it indicates the following for display 'I can edit' 'unpublished' .

'update' access=1 by workflow_access-grants: 'Wobbler Syndrome'

This looks great, but when I click to view the node (node/123) I see the following:

'view' access=1 by workflow_access-grants: 'Wobbler Syndrome'

I don't see an 'update' access=1 message anymore, and I am not permitted to edit the node. Instead I get the Access denied page. I have tried rebuilding permissions but problem continues.

Can anyone advise me on the best next step to take to try and see what is keeping me from updating this node? This workflow used to work just fine. I am current with all module updates and am using Drupal 6.17.

Mark

Comments

rdeboer’s picture

rdeboer
Location Melbourne
commented

Hi Mark
Just so that I get a clearer picture...
When you go to Administer >> Site configuration >> Module grants, what does it say at The following content access modules are currently enabled: ....? Just workflow_access or are there other modules involved?
What does the debug output say when you type in your browser address bar: "node/123/edit" ?
Rik

msellers’s picture

msellers commented

"The following content access modules are currently enabled: workflow_access".

"Access denied
You are not authorized to access this page"

rdeboer’s picture

rdeboer
Location Melbourne
commented

Ok... so there's only one "official" content access module in play, which means that the whole OR-ing or AND-ing issue doesn't apply.
There could still be another "unofficial" module throwing a spanner in the works with respect to access permissions.... Have a look at your list of modules and see if you can spot any "suspects".

Also, while Moudle Grants does a fine job 99% of the time, there are cases where unexpected results may occur. To fix these, I suggest you apply the one-line patch described here: http://drupal.org/node/408816, section For the experts.

Hope that helps!
Rik

msellers’s picture

msellers commented

Thanks Rik. I jumped into the module_grants code and found where the permission was being denied. I reassigned some filter settings and set the editor role to have only Filtered HTML access. These node was authored with Full HTML access and therefore became uneditable for this user role. I reassigned Full HTML access to this role and the problem is fixed.

Anyway, thanks for embedding the debug messages in your code. It helped me stay on track to understand this problem.

Mark

rdeboer’s picture

rdeboer
Location Melbourne
commented
Status: Active » Closed (fixed)

Cool -- so there was another access module throwing a spanner in the works: the input filter!
Glad it's all working for you now.
Closing.