In some scenarios, a user may have access to a full biblio node but not see that node in a view for example. Steps to reproduce:
1. create a biblio node
2. create a user and give the user the permissions:
- Bypass content access control
- Administer content types
- Administer content
(in theory these permission give you super powers over nodes and you would expect to access all nodes on your site)
3. go to node/1 (the biblio node you created above). the user should see that node
4. create a view of biblio nodes
5. note that the user sees an empty list, unless the permission "Access Biblio content" is granted to the user.
Requiring the permission "Access Biblio content" to view biblio nodes in views when the nodes can be viewed without this permission is misleading. I'm not sure why this permission exist to begin with. People who want to do content access on a content type or a node level can use dedicated contrib module such as https://drupal.org/project/content_access.
Proposal: remove the permission "Access Biblio content"
Comments
Comment #1
rjerome commentedLet me look into that a bit, that permission may just be a throw back to 5.x and 6.x days, and no longer be required. To be honest, I'm not ever sure where that's coming into play if you are using Views (I'm guessing due to biblio_query_node_access_alter() ) but I will have to check.
Comment #2
mikemadison commentedI"m having a similar problem, unauthenticated users on my site cannot see biblio pages / content, and I can't give the "access biblio content" permission to any role but an admin. When I click on the perm and save the page, the page comes back without the box checked. Have tried clearing cache and rebuilding permissions.