Hey salvis and all,

I've had a very puzzling issue come up. I've used ACL to grant several users 'view' access to a node. They should be able to view the node, but they are receiving Access Denied errors. However, the Devel Node Access and Devel Node Access by User blocks claim that each of these users should have access.

Is it possible for the Devel Node Access blocks to be incorrect? Any other reason why Devel Node Access would say one thing, but actual experience would be another?

I should also mention that I'm using the latest stable version of Content Access (6.x-1.2) in conjunction with ACL. (The 'Access Control' tab of Content Access also shows these users granted 'View' access.) The Drupal core version I'm using is a little old (6.14), but I don't see how that would affect this.

I've attached a Devel Node Access screenshot that shows the users who should be granted view access. All of them are receiving an access denied message (except for the one with administer nodes permission).

Thanks,
Ben

CommentFileSizeAuthor
DNA.png77.69 KBBenK

Comments

salvis’s picture

salvis
he/his
commented

That's very puzzling indeed. DNA and ACL for D6 have been stable for quite a while and I'm not aware of any issues with either of them. DNA double-checks its findings with core, and it would report any differences.

Are you sure you don't have any other module that might deny access?

I see several possible courses of action:

– disable all modules except for CA, ACL, and CNA and check what happens

– try to reproduce the error on a newly-installed test site with just those three

– install a debugger and find out where the drupal_access_denied() call comes from

– use Devel's dbacktrace() (don't remember exactly what it's called) to find out where the call comes from

robbmlewis’s picture

robbmlewis commented

I ran into a similar problem where I thought everything was set up right. I finally found that the format the content was in (full html) was not a format that the user could edit (filtered html). Once I fixed that and gave the user the permission to use full html, it worked.

salvis’s picture

salvis
he/his
commented

Yes, this does happen, but it's clearly reported by DNA for each user.

BenK's screenshot doesn't show this.

Pongolyn’s picture

Pongolyn commented

The issue #2 describes just happened to me (although it didn't seem to matter whether I had ACL enabled). I had a newly-created role that hadn't been granted access to use the Full HTML editor, so attempts to edit the page or revert revisions generated an Access Denied page, even though all other permissions appeared normal.

Going to Admin>>Site Configuration>>Input Formats and adding the role to the Full HTML Editor list solved the problem. Thanks so much for posting this!

salvis’s picture

salvis
he/his
commented
Issue summary: View changes
Status: Active » Reviewed & tested by the community

Nothing to commit, just mark this for keeps.

salvis’s picture

salvis
he/his
commented
Status: Reviewed & tested by the community » Closed (outdated)