Without this module enabled, the permission to access/ view nodes is managed using the 'access content' permission setting under the 'node module' section on the form 'admin/user/permissions'. So, if the module is enabled, shouldn't that permission be grayed out (disabled)? Does that setting overrule the 'view (all/ own) nodes' settings of this module?

Comments

royerd’s picture

royerd commented

I don't think that's right, not DB. The access content is general. This view own adds a more fine-grain to things. We see now view own and view all for the specific content. But this applies to authorship, not to the general access. At least that's the way I understand it.

I can't understand why this module is not more widely used. I have several sites now that I've built "submission managers" for where "own" is critical.

I recently discovered the problem with the "blog" content--have to use the DEV version.

kenorb’s picture

kenorb commented
Issue summary: View changes
Status: Active » Closed (outdated)

Closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.