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

Command icon 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

good_man’s picture

Title: Initial GUI settings don't reflect current permission status » New roles are unchecked in access page by default
Version: 6.x-1.2 » 7.x-1.x-dev
Component: User interface » Code
Category: support » bug
Priority: Normal » Major
Status: Active » Needs work

Yes this needs a quick fix, any patches are welcomed.

good_man’s picture

Issue tags: +Needs backport to D6
gisle’s picture

Version: 7.x-1.x-dev » 8.x-1.x-dev
Issue summary: View changes
Status: Needs work » Active
Issue tags: -Needs backport to D6 +Needs backport to D7

Drupal 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.

gisle’s picture

Priority: Major » Normal

Downgrading priority.

gisle’s picture

Version: 8.x-1.x-dev » 2.0.x-dev

This should go into the version compatible with Drupal 10.

kkaya’s picture

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?

steven jones’s picture

Title: New roles are unchecked in access page by default » Ensure that new roles are granted access by default
Version: 2.0.x-dev » 2.1.x-dev
Category: Bug report » Task

I 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.

steven jones’s picture

Status: Active » Needs review
Issue tags: -Needs backport to D7

I'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,

steven jones’s picture

Title: Ensure that new roles are granted access by default » Ensure that new roles are not granted access by default

  • steven jones committed 0feedc3a on 2.1.x
    test: #575606 Ensure that new roles are not granted access by default
    
steven jones’s picture

Status: Needs review » Fixed

Fixed!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.