Hi,
I think the following is a bit confusing and maybe its possbile to address it. Or it can just be that I am unveiled as a drupal noob :)
In the screenshot below you see the content access settings for a newly created content type.
http://screencast.com/t/qOnrYsJt0IS [now 404]
The boxes for webmaster and professional are unchecked but this does not reflect the real situation i.e. the content type *is* viewable by these 2 roles
Only if you press save the content type will not be viewable by these roles.
On another not I read that access modules can only GRANT permissons, not deny them. So how come that Content Access can deny the view access on its own?
I have the drupal 6 permission "access content" granted for the role webmaster and professional so how come that Content Access can overrule drupal itself?
Thanks for clarifying this! Its one of the hard parts in drupal and I am trying hard do understand it
Regards, Tom
Issue fork content_access-575606
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #1
good_man commentedYes this needs a quick fix, any patches are welcomed.
Comment #2
good_man commentedComment #3
gisleDrupal 6 branch is no longer supported. Patches go to latest branch.
But I agree that this is unexpected behaviour. As always, a patch to fix it would be welcome.
Comment #4
gisleDowngrading priority.
Comment #5
gisleThis should go into the version compatible with Drupal 10.
Comment #6
kkaya commentedHi - thanks for this great module. I was not able to reproduce this issue with Content Access 2.1.0-rc1 on Drupal 10.4.
I tried creating a new content type, unchecking the anonymous and authenticated roles from "View any" and "View own" on the "Access control" tab of the new content type, and then verifying an authenticated user could not see content of the new type. Then I created a new role and assigned it to the user, but the new content for the new type was still not visible to the user with the new role.
Are there other steps to reproduce this issue or is it resolved?
Comment #7
steven jones commentedI suspect that this bug is not a bug in the 2.1.x version of this module, but maybe we should add a super simple test that sets everything up, with 2 users, one with a role that confers access, and one with a role that does not. Then we should add a new role, completely unrelated to the others, and see that the situation is the same, that the first user can access, and the second still, cannot.
Comment #9
steven jones commentedI've added a test, as described, and it passes! So I don't think this is an issue any more, it would be weird if it was tbh,
Comment #10
steven jones commentedComment #12
steven jones commentedFixed!