Before using the module, you should read the installation instructions. Failure to install or uninstall this module according to instructions may cause errors in your site.

Domain Failed to Load Error Message

If you receive a message indicating that the 'Domain failed to load' this indicates that the settings.php file has not been properly configured. Follow the instructions at Configuring settings.php.

Rebuilding Content Access Permissions

After installing the module you may be asked to rebuild the content access permissions. This is a normal part of the process when adding a node access module to an existing site.

Domain Access Isn't Properly Restricting Access to Content

Node Access rules never apply to user 1 (the site admin) or to users with the 'administer nodes' permission. As such, these users will always be able to see all content on your site(s). To verify that Domain Access is working correctly, you will need to turn on its debug mode or view the site as a user without this permission. You may also enable the 'Enforce rules on administrators' setting, which will apply Domain Access restrictions to all users.

The easiest way to debug this behavior is to download Devel module and enable Devel Node Access. Use the provided Devel Node Access by User block to see how node access rules are being applied.

Problems Assigning Content to Desired Domains

When a user creates content, that content will automatically be assigned to the currently active domain unless the user has specific privileges to be able to assign domain access. Under advanced setups, the ability to edit content for a specific domain can be segregated from the typical Drupal privilege to 'Bypass content access control.'

For more information about Domain Access privileges, see section 3.

For more information about node_access(), see http://api.drupal.org/api/group/node_access/6

Using Multiple Node Access Modules

Node Access is a complex issue in Drupal. Typically, sites will only use one node access module at a time. In some cases, you may require more advanced access control rules.

Two important issues to understand are:

  1. User 1 and users with the 'Bypass node access' permission are not subject to node access rules. See section 4.3.3 for more details.
  2. Node Access is a permissive API. If you use more than one Node Access module (such as Organic Groups), if either module grants access, users will be given access.

For more, use the Devel Node Access module to help understand your access rules.

Changes to these core behaviors require custom code solutions.

Logging In To Multiple Domains

The Domain Access module allows the creation of domains with different hosts. However, security standards dictate that cookies can only be read from the issuing domain.

As a result, you may configure your site as follows, but when you do so, users cannot be logged through a single sign in.

  • example.com
  • one.example.com
  • myexample.com
  • thisexample.com

While example.com and one.example.com can share a login cookie, the other two domains cannot read that cookie. This is an internet standard, not a bug.

Note: See the INSTALL.txt for instructions regarding Drupal's default cookie handling.

Cron Handling

When Drupal's cron function runs, it operates on the domain from which the cron.php script is invoked. That is, if you setup cron to run from:

http://one.example.com/cron.php

In this case, Domain Access will check the access settings for that domain.

This behavior has been known to cause issues with other contributed modules. As a solution, we normally disable Domain Access rules when cron runs.

If you encounter any cron-related issues, please report them at the Domain Access Issue Queue

'Promote to Front Page' and 'Sticky' options

These options function on the node level and, as such, cannot be individually set on a per-domain basis. In other words, promoting a node to front page and/or making a node sticky will apply on all sites.

A workaround is to handle these options via Taxonomy (Term Reference) with a term for each domain so that Views can be constructed that respect the Taxonomy term, instead of the node setting.

Links on affiliate domains go to the published domain instead of current domain

To prevent links from being rewritten, enable the Domain Source module. Make sure source domain for each page is set to 'Use active domain.' You can also update multiple pages from the Affiliated Content pages provided by Domain Content.

Updating Your Site

For upgrade instructions, see the provided UPGRADE.txt file included with the module.

Comments

kapow99504’s picture

Where is section 4.5.1 Cron Handling?

agentrickard’s picture

Removed now.

captaingeek’s picture

can I have some more details on 'Promote to Front Page' and 'Sticky' options?