I discovered two heavy bugs, with content access - without warnings about
1) I use the domain access module. Together with content access this result in a visibility of a node with anonymous view rights to all domains, when published to front page. A node with limited access dosn't show this behaviour and is only visible to domains, where enebaled for.
2) Just because of this bug I wanted to uninstall content access. Here again happened something strange to to nodes and views with anonymous view rights: The all disappeared from the site non logged in. Once logged in as user the nodes were visible again.
Conclusion: there must be anyhow a bug with content access, when it comes to anonymous content access....
Thanks for a tipp how I how to uninstall content access without leaving leaving a mass of no more visible views and nodes to anonymous visitors....

Comments

good_man’s picture

good_man commented

I didn't quite understand what you did after enabling both modules. You created some domains and added content, then you granted view content to anonymous users, but then the problem occur as anon. users haven't been able to see those content? did I understand it correctly?

wisniewski’s picture

wisniewski commented

The problem I suppose is quite simple. In my case:
2 domains: example.com, fbapp.example.com
I wanted to deny view for certain type of node, only authors can view:
- anonymous: (anonymous - 0, authenticated - 0)
- own: (anonymous - 0, authenticated - 1)

Modules: Domain Access, Domain Theme (I use theme for facebook apps, no access controll with it)

If I disable Domain Access, Content Access works correctly.

wisniewski’s picture

wisniewski commented

This bug must be pretty old:
http://drupal.org/node/764904

jan.s’s picture

jan.s commented

I had the same problem. After uninstalling Content Access you must rebuild the permissions (/admin/reports/status/rebuild).

The problem occured suddenly after many months in my installation. I fixed it by uninstalling Node Access.

http://drupal.org/node/1561364

marksward’s picture

marksward commented

Does setting 'Give content node grants priority' to -1 under advanced when viewing a content type structure resolve this for you?

gfdickinson’s picture

gfdickinson commented

Setting the content node grants priority worked for me.

gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
commented
Assigned: choy » Unassigned
Issue summary: View changes
Status: Active » Closed (outdated)

This issue has not received any updates in the previous 8 years. If you believe it to still be relevant, you are encouraged to reopen the issue and update it.

If you got an email about this Issue status update, it is because you at one time (possibly a very long time ago), subscribed to it. To learn how to unsubscribe yourself, please visit: https://www.drupal.org/project/webmasters/issues/3142987