- 🇳🇴Norway gisle Norway
This should go into the version compatible with Drupal 10.
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
Active
2.0
Code
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.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This should go into the version compatible with Drupal 10.