Posted by no_longer_active_19 on November 20, 2012 at 5:13am
How can I stop the core node permission "view published content" from overriding settings in content access module?
Do I need to use taxonomy- why isn't there a view published content per node?
And what is the difference between "view published content" and "access the content overview page" because
when setting it to the latter I get a permission access denied on basic pages when it seems I should get at least
the overview?
Comments
You can set the permissions
You can set the permissions in /admin/people/permissions
"view published content" is the name of permission to set which user's role can access the published content.
"access the content overview page" is the access for content overview page in admin section /admin/content
Be specific what you want to achieve.
-Imran
already set permissions
They are pretty straightforward but it doesn't change the fact if you have view published content de-selected in node permissions for say anonymous users but in content access you have certain content you do want viewed the core will over ride those settings.
You can only choose view published content for ALL pages and not individual because regardless what settings in content access they will be over ridden.
How can I be more specific?
my advice For newbies like me creating access settings
I've found I have to select view published content for all users in node core permission settings and then use access control module rather than the other way round where all your pages are access denied and you try and enable access through content access module because it won't work.