All Sites must reside on the same server If using sub-domains or domains, directories must be able to access your main installation system directory. Please see Setup Domains and Sub-domains for more information.
It is recommended that you Create a Site before setting up the domain or sub-domain.
Create the domain or subdomain using your webhost’s tools. Typically this will automatically create a new folder on the server that the site’s files will be served from. Please contact your host if you need assistance with this step.
The new folder must allow files within it to access your installation’s system folder. Check with your host to ensure you don’t have “open_basedir” or other restrictions in place which could prevent this.
Copy the following files from your first (default) site’s folder to your new site’s folder. We’ll call the new site domain2 for the purposes of this example.
Your single-site installation might have looked like:
└── domain1.com ├── admin.php ├── index.php ├── images ├── system └── themes
Now that domain2 has been added, your folders might look like:
└── domain1.com ├── admin.php ├── index.php ├── images ├── system └── themes └── domain2.com ├── admin.php └── index.php
Open domain2’s new admin.php file (this is the file that allows Control Panel access on the new site) and make the following changes:
Tip: In some multi-site situations, you may not want to allow Control Panel access from anyhere other than domain1. This file can be removed in those cases.
Update the $system_path variable to indicate the path from this file to your installation’s system folder. Typically this can be a relative path, but some servers may require a full, absolute path. For example, given the folder structure above:
$system_path = '../domain1.com/system/';
Uncomment the following $assign_to_config variables. Set the Short Name of the site this file will log into, and this file’s URL. For example:
$assign_to_config['site_name'] = 'domain2_short_name'; $assign_to_config['cp_url'] = 'http://domain2.com/admin.php';
Open domain2’s new index.php file and make the following changes:
Update the $system_path variable to indicate the path from this file to your installation’s system folder. Typically this can be a relative path, but some servers may require a full, absolute path. For example:
$system_path = '../domain1.com/system/';
Uncomment the following $assign_to_config variables. Set the Short Name of the site this file will display, the URL of this site’s admin.php file, and the main URL of the site (without index.php). For example:
$assign_to_config['site_name'] = 'domain2_short_name'; $assign_to_config['cp_url'] = 'http://domain2.com/admin.php'; $assign_to_config['site_url'] = 'http://domain2.com';
If you have multiple sites, you may prefer that when a user logs into one site, they are logged into all sites.
Settings --> Security and Privacy: make sure the Website Session type is set to Cookies only for each site you want to include.
If your sites are in separate subfolders (
https://example.com/site2/index.php) or separate subdomains (
http://site2.example.com) you can simply set the cookie domain for each site to the top level domain.
In the case of
http://site2.example.com type URLs, the cookie domain should be .example.com.
Logging in on any of the URLs would result in cookies that can be read on any subfolder or subdomain of the example.com URL.
However, cookies for one domain cannot be set from a different domain. If your sites use different domains, you’ll need to use the multi_login_sites configuration override . Add the following to your system/user/config/config.php file, modified according to the domain names used by your sites:
$config['multi_login_sites'] = "http://www.example.com/|http://www.sitetwo.com/|http://www.sitethree.com/";
If you use an index file such as
index.php in your URL, you should include it in the URL:
$config['multi_login_sites'] = "http://www.example.com/index.php|http://www.sitetwo.com/index.php";
Now when a user logs into the frontend of one of the sites, the login routine will invisibly loop through each URL in the configuration, redirecting to that site, setting the appropriate cookies, and then cycling through to the next site. Once the user has been logged into all of the sites, they’ll end up back on the starting URL. The login redirects will be virtually unnoticable.