Closed (outdated)
Project:
Content Access
Version:
6.x-1.2
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
30 Nov 2009 at 16:21 UTC
Updated:
24 May 2020 at 13:49 UTC
Jump to comment: Most recent
Comments
Comment #1
CardinalFang commentedSame issue here. Anonymous users can see all content no matter what I do.
Comment #2
CardinalFang commentedI should have mentioned that I'm also using Domain Access. After installing Domain Access Advanced my desired content permissions started working.
Comment #3
stephenhendry commentedGetting the same issue.
Comment #4
stephenhendry commentedThis issue for me was that the workflow module was conflicting with this. Setting the advance option to a postive number fixed this issue for me.
Comment #5
salvisInstall the Devel Node Access module (part of the Devel module) and enable its debug mode to see what is happening.
Comment #6
greta_drupal commentedgazelle, thank you for that! worked for me; and seems to be playing nicely with my Views content access permissions. i was sweating this one (with live site).
For others, to clarify: Setting a priority number (I used 1) under Advanced fieldset of the Content Access settings for a particular content type.
Comment #7
jami3z commentedHave the same issue here. Anonymous users can see all content no matter what I do. I'm pulling my hair out! I'm not using workflow, domain access or any other module that might conflict. Have even set to a positive number.
Comment #8
jami3z commentedIt now works for me. Woo hooo! Stumble across this post settings page under the content section in admin, and found a Node access status rebuild button gave it a click and presto, it now works.
Comment #9
WeRockYourWeb.com commentedThat did it for me as well - thank you JamieNoTweet!
Browse to /admin/content/node-settings and select the "rebuild permissions" button after setting your new content access restrictions.
Comment #10
salvisIt's nice that this manual work-around works for you all, but it would be even nicer to investigate and fix the problem (see #5 above)...
Comment #11
gisle