Posted by Crell on September 24, 2012 at 12:18am
Project:
Drupal core
Introduced in branch:
8.x Description:
In Drupal 7 and earlier, Drupal supported automatic multi-site functionality by means of different directories under the /sites/ folder. Specifically, directories there would match to the incoming domain name of a request, allowing multiple sites to be hosted in the same Drupal site. Drupal 7 also introduced a /sites/sites.php file to allow aliasing of incoming domains to specific path names.
As of Drupal 8, the multi-site functionality does not activate unless a /sites/sites.php file is present. If there is no sites.php file, then only /sites/default will be checked and no other multi-site functionality will be triggered.
Impacts:
Site builders, administrators, editors
Comments
For anyone who wants to save
For anyone who wants to save the time that I lost in discovering this:
Drupal 8 multisite and Acquia Dev Desktop
will not play together at all unless you manually copy the example.sites.php into sites.php (no change needed). Weird half-installations happen otherwise.
Drupal 8 multisite and Aegir
may have the same issues.
Both Acquia and Aegir do multisite ONLY and ignore 'default' normally. D8 now does 'default' ONLY unless the opt-in described here is applied.
It's good to force folk to get familiar with sites.php now though...
.dan. is the New Zealand Drupal Developer working on Government Web Standards
Multisite can be done the same way as before
sites/ABC can still be a directory and contain the modules and themes reqd for the site with its own settings.php and files folder
https://github.com/drupal/drupal/blob/8.x/core/INSTALL.txt (look for MULTISITE CONFIGURATION)
Bringing modules / themes / profiles into the root directory also removes the folder structure required for multisite if you dont want it altogether. Good work !!
Mukesh Agarwal
www.innoraft.com