New roles are unchecked in access page by default

Created on 12 September 2009, almost 16 years ago
Updated 28 April 2023, over 2 years ago

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

πŸ› Bug report
Status

Active

Version

2.0

Component

Code

Created by

πŸ‡§πŸ‡ͺBelgium buckley

Live updates comments and jobs are added and updated live.
  • Needs backport to D7

    After being applied to the 8.x branch, it should be considered for backport to the 7.x branch. Note: This tag should generally remain even after the backport has been written, approved, and committed.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡³πŸ‡΄Norway gisle Norway

    This should go into the version compatible with Drupal 10.

  • πŸ‡ΊπŸ‡ΈUnited States kkaya

    Hi - 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?

Production build 0.71.5 2024