Created test installation without using any SSO modules. Just sharing domain cookie. All DA configuration is done on first site (login.test1.com). The second site is www.test1.com - no DA modules set up. Single database installation.

When content is created, it is assigned to specific site - in my test situation - www.test1.com ONLY. (Without publish to all affiliates.) By sharing domain cookie in settings.php, I am logged in as in first site, as well as in the second site. But content created for second site (www.test1.com) is displayed on the first too. The result is the same, whether content is created from login.test1.com or www.test1.com.

Is this normal result, or I did miss something in configuration?

Comments

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

From README.txt

----
4.3.3   Enforce Rules on Administrators

When using Node Access modules, user 1 (the super-admin) and users with
the 'administer nodes' permission are not subject to node access rules. This
is a design feature of Drupal, and it can lead to confusion when viewing your
site as an administrator.

To help with this confusion, the 'Enfore rules on adminstrators' setting can
be enabled. This setting forces Domain Access rules to be applied _even to
users who can administer nodes_.

The default setting is OFF, but if you regularly login as user 1 or a user with
the 'administer nodes' permission, you may want to enable this feature.

NOTE: This feature _only_ applies Domain Access rules. if you are using
multiple node access modules, not all rules will be applied.
agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

I do not know how SSO module interacts with the code. And the situation you describe does not make sense to me. Are the two sites sharing a {node} and/or a {node_access} table?

It is also possible that your DNS or settings files are not set up correctly, and the same site is actually loading at both URLs.

j2b’s picture

j2b commented

As to comment #1 - yes I was aware of such thing, but didn't expect, that it can influence content display. Although, can confirm, that if separate non uid=1 user is used, the situation remains the same. Creating content for site No2, it is displayed on site 1 too. Further digging resolved situation. Main problem was in Domain > Node settings form, where checkboxes on Domain node types section had to be removed. If these checkboxes are active, then all selected node types will be published to all affiliates, despite exact domain settings.

Although, if content is created with elevated permissions, like admins, then there is possibility to remove checkbox in content type publishing options - Send to all affiliates. But if the user is with restricted permissions, then it has an opportunity to select specific domain, but can not influence this Send to all affiliates function.

Does permissions edit/delete domain nodes influence DA module's domain reccords, or it is somehow connected to node module permissions?

As for comment #2 - SSO is not a question. It was just a test, where I wrote how I managed user logon sessions without additional SSO module. The only difference, is if I set up cookies handling in settings.php file, all registered sites should be within the same 2nd level domain. It probably would not work with different 2nd level domains. But if I needed to host different domains, then it is a problem to solve single sign-on features. SSO module requests at least 2 different sites built on multi-site drupal setup, even sharing the same table. Because one site should be controller, but the others - clients. In DA module you manage all the modules for all sites in one place and you can not enable controller and client modules, as it throws an error, that only one module per site can be enabled. But I managed to setup SSO to work. In that experiment, there was a problem, that publishing to second domain site didn't work, because second domain is outside control of DA module (it is in sudirectory of ../sites folder as per SSO settings). May be as you wrote in second comment, sharing node table could be a solution.

Originaly I wanted to develop a site, where user can create their own site inside drupal without involving administration tasks to create another multisite. The main reason was that I wanted to give my users possibility to define their own domain names on DNS side and link them to my drupal site. Modules like OG offer such functionality, but they do not offer to link group site to separate domain. They allow www.test1.com/subdomain models, which is not what I expected to achieve.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

The node-settings are non-optimal, but documented.

As to this: Does permissions edit/delete domain nodes influence DA module's domain reccords, or it is somehow connected to node module permissions?

These are DA permissions, stored in the {node_access} table and only invoked via hook_node_grants() is the user has the permission. See 3.3 of the README.

Glad you got it working properly.

j2b’s picture

j2b commented
Status: Active » Closed (fixed)

Thank you for your comments and additional info.

muerteno1’s picture

muerteno1 commented

I have same problem problem, i have 3 domains:
exe.com
aaa.exe.com
bbb.exe.com

all instaled in single database. I use Latest version of drupal 6 and DA. I turned off affiliates to node types in "Node Settings" and when i create new content and check only some subdomain i see it on all 3 domains. I was checking as a logeed and anonymous user.

I was trying to find some help but all anserws was for difrent version on drupal or didnt worked for me. Somone mebby know how to fix it / where should i check?