Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Hello, I have been setting up a multisite drupal installation using the Domain Access module.
I have run into some problems installing the site. I have separate settings.php files for each site in their respective sites/* dir. I chose not to share the menu, block, blocks_roles tables. Using the table prefix array. I created the unique tables for each site.
The reason is that I want unique menus for each site and unique page layouts. I do not want a site admin to be able to edit another site's blocks and menu. Since I have been working with the Domain Access module I have been unable to get the site configuration working correctly. I can have unique site names, but for some reason I cannot change the footer, frontpage or other site options for both sites.
I go to batch updating->site frontpage settings and two different node paths are used for each site; however, no matter which site I go to, the default site frontpage is shown.
My other problem is trying to display the correct menu. I have created two different menus for each site called "Main Menu". I am using Taxonomy Access to control if the menu can be seen by anonymous users and whatnot. I manually installed the multiple node access patch by deleting and adding code blocks. I can only seem to get one site's menu to display to anonymous users at once. If site1 shows the menu, then site2 doesn't. When I go to site2 and re-save the blocks settings...site2 menu is displayed correctly, but site1 isn't... This is happens no matter what I do.
Please help. I have been struggling to get this multi site installation working for about 2.5 weeks now.
Comments
Comment #1
GregL83 commentedI seem to have gotten the menus working. The cache tables shouldn't be shared. The menu was cached in the database and wasn't updating correctly for each domain.
I am still having issues getting the correct frontpage to display. The site settings for the primary domain always show for both with exception to title.
Comment #2
agentrickardDomain Access and Drupal Multisite are two different things entirely. You cannot mix and match the two. For instance, DA requires that you have only one settings.php file.
It sounds to me like Domain Access is not the right solution for you. DA is not meant to replace a multisite configuration; it is meant to allow publishing across a family of related web sites.
Comment #3
GregL83 commentedHmmm. I do need to share some content across my domains. I need to share some stories, events, and products; however, not pages. I am also using taxonomy access with the drupal node patch installed (multiple node access).
So, your saying that I need to delete my second site folder (in sites directory) and only keep the default folder and settings.php?
I am guessing that I will then remove the prefix array (settings.php) and set it back to default.
Is is possible to not share particular tables with the domain access module? I was having trouble using the prefix domain access settings. I do not want to share menus and blocks across the domains.
Thanks for your response. I have read many of your comments throughout my Drupal Journey.
Comment #4
GregL83 commentedNOTE: I have setup a local version to do more testing. I reset the 'sites' dir to installation conditions. I no longer use a drupal multisite setup and I no longer have non-shared tables. I installed drupal from scratch and setup DA. After DA installation I created a domain record. I then used batch updating to set the footer of site1 and site2.
My problem is that site1's footer is still shown in site2....I cannot set the site configuration independent for each domain...
Comment #5
agentrickardPlease read the provided documentation for the entire suite of modules. Especially Domain Configuration.
Comment #6
GregL83 commentedThank you for the hint *.
For anyone who runs into this problem. The domain access modules that come included need to be installed separately to function correctly. Installation involves requiring the module's configuration file at the bottom of settings.php.
* Slap in the head with the book of simple solutions.
Thanks again ;) .
Comment #7
agentrickard