Thank you for this excellent module. I've been mulling over the documentation for a couple days but parts of it are a bit over my head. I would appreciate if somebody could comment on my situation.

MY PROBLEM: I have an active standalone Drupal site (let's call it Site A) with about 6,500 members. I would now like to expand the concept into a few separate but related Web sites.

MY GOAL: I would like all the sites to share all users and some--but not most--content so Domain Access seems perfect. However, I wouldn't want to make my existing Site A the primary domain.

MY QUESTION: So would I create a new drupal multisite installation with my intended domain access "Primary domain" as the primary domain? And then migrate Site A as one of the parked domains in the multisite?

Thanks.

Comments

agentrickard’s picture

No. Domain Access is used instead of multisite. You just have one site. One settings.php and one database.

You want to read section 2 of INSTALL.txt very carefully. Set DOMAIN_SITE_GRANT to FALSE. Install on a new domain, example.com.

This will assign all current content (and users) to example.com. Then add 'Site A' as a.example.com (or whatever). It will have no content, however. You could then write a hook_update_N to "move" the content you need to. Or use Domain Content to selectively move content.

sockah’s picture

Thank you AgentRickard. I see how I was thinking of Domain Access incorrectly by confusing it with a multisite install. I'll reread the manual and then try a test run.

One thing I'm particularly concerned about is maintaining the URLs because of search engine traffic. I'll dig through site to find out more.

Oh and AWESOME MODULE!

agentrickard’s picture

There are some threads that talk about path aliasing across multiple sites, which is the primary issue for most people, and solvable with Domain Prefix.

sockah’s picture

Thank you. I'm beginning to work my way through all available documentation and experimenting with a test install slowly but surely. This is an impressive module that really pushes what I had thought possible with Drupal.

Is there any drawback to simply parking domains on the primary domain via something like Cpanel--which effectively points them to the same document root--as opposed to directly editing the httpd.conf file?

croryx’s picture

I have two sites that are setup this way using Cpanel. For both sites DA is managing a set of subdomains so I just add subdomains in Cpanel and point them all to the same document root. There is some additional discussion of this in the queue somewhere.

agentrickard’s picture

I wouldn't park on the Primary Domain, since that is used as the fallback in case all other checks fail.

You can use Domain Alias to "register" parked domains to a URL other than the primary, but all unregistered domains that pass to Drupal default to the primary domain.

agentrickard’s picture

Status: Active » Closed (fixed)
abendy’s picture

#1 - "No. Domain Access is used instead of multisite. You just have one site. One settings.php and one database."

This thread has alerted me to what may be causing errors for my installation with DA.

I have a multisite installtion and for 2 of these sites I am attempting to use DA- blog.domain.com and studio.domain.com (the root level domain is a completely different site)

Does your comment mean that DA isn't possible for multisite installs and I should install a new instance in a sub directory and run the site from /sites/all/?

Thanks

UPDATE: I've just successfully installed Drupal in a sub directory, ran it off /sites/all/ and used DA to publish content across domain.com and sub.domain.com. My question still stands for confirmation- is it possible to run DA in a multisite instance?

abendy’s picture

Status: Closed (fixed) » Active

Anybody?

agentrickard’s picture

Issue tags: +handbook

It is possible. In that case, you want any domains using Domain Access to be accessed through the 'default' settings folder. Any domains that should be separate need to go in a named settings folder.

E.g.

You have the following domains pointed at your multisite instance.

-- example.com
-- one.example.com
-- myexample.com

You want to run multisite, but only for the first two sites. You would have the following directories in /sites:

/sites/default
/sites/myexample

This will load myexample.com like a standard multisite, and the other domains from a Domain Access multisite.

In this case, put the domain module inside sites/default/modules.

abendy’s picture

Thank you!

agentrickard’s picture

Status: Active » Closed (fixed)