Closed (fixed)
Project:
Domain
Version:
6.x-2.7
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
8 Nov 2010 at 19:35 UTC
Updated:
12 Jun 2011 at 20:14 UTC
Sorry if this has been brought up and answered before. I've looked through the issue queue and didn't see anything exactly like this.
If a user goes to site1.domain.com/node/1234 (node/%n or node/nid), the content is visible regardless if it has been published to that node. I use domain access and domain source. I am guessing I have something misconfigured or some permission(s) set wrong. I've read through the documentation and can't seem to grok what I could have set up wrong.
BTW - the database tables domain_access and domain_source seem to be correct.
What should I look for or what documentation should I re-read.
Thanks.
Brett
Comments
Comment #1
agentrickardTwo possible answers here.
1) The user is user 1 or can 'administer nodes'. Those users bypass node access rules. The solution is to enable 'Enforce Rules on Adminstrators' -- section 4.3.3 of README.txt.
2) The node is assigned to 'all affiliates', which does exactly what that says, displays the node on all sites. When 'all affiliates' is checked, the site-specific assignment is only used for editorial control and URL rewrites. Check 4.3.1 of README.txt for some more detail.
Failing that, see 4.3.2 the debugging status, which will give you an idea what is going on.
Note also that if you are using more than one node access module, if any module grants access, you get access.
Comment #2
bstoppel commentedThanks for the quick response.
It turned out to be the Taxonomy Access Control module that was messing things up. http://drupal.org/project/taxonomy_access
Comment #3
bstoppel commentedMarking fixed.
Comment #4
croryx commentedSee the new documentation page Why are nodes accessible on domains they are not published to? for a full list of reasons why nodes may be unexpectedly accessible.