Skip to main content
Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Code code:"if (foo != bar)"
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Saves in:saves
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with
Search options answers only not deleted user 2618

Use it for the module for running a group of affiliated sites from one installation and a single shared database.

0 votes

Domain Access separate home page per domain does not work

I am using the technique you labeled "option 2" above; it works fine. I put "node/835" in for the site frontpage for one domain, and that node is in fact shown as the front page for that domain. One …
greg_1_anderson's user avatar
1 vote
Accepted

Shared Database With Domain Access and Multiple Accounts With Same Email

You should not use Domain Access unless you are planning on sharing users and content between the different domains. In your instance, you do not want to share users -- and yes, you would have proble …
greg_1_anderson's user avatar
2 votes
Accepted

Specifying the default database to store new field tables in

Unfortunately, Drupal was not designed to work this way. The only way to figure out where to put each table would be to carefully inspect each new module and adjust your settings in advance of enabli …
greg_1_anderson's user avatar
1 vote

Single site vs Sub-sites vs Multi-site installation + Scalability

There are many possible ways to build out a site like this. Right off the top, I would recommend against using a multi-site setup. c.f. Drush pm-update and multisite. If you did want to use multipl …
greg_1_anderson's user avatar