I'm considering using the domain access module but would like to know, before I get too far down the track, whether it behaves as I want it to.
My aim is to use a single code base and a single database to host a number of sites.
Having multiple copies of the same same tables with different prefixes would not suit my purposes.
Having data from one site displayed to users of another site would not suit my purposes.
My questions...
Is any of the data inappropriately global (e.g. taxonomy, lists of users, roles, etc) ?
If five of my customers want ubercart would a single install behave as though it were five independent installations?
Note: I'm currently using my own CMS and am in the process of switching to Drupal - so I'm a bit of a noob as far as Drupal is concerned.
Comments
Is any of the data
Yes, all that will be global.
Nope, it will behave as if it were one installation as far as the back end is concerned, though DA will let you restrict particular content to particular subsites.
If you want sites to behave more independently, you probably want to use Drupal's standard multisite system rather than Domain Access. You'll either have to use multiple databases or play table prefix games, though.
The Boise Drupal Guy!
Thanks Garrett, you saved me
Thanks Garrett, you saved me going down a dead end.
I decided to do my own multisite hack using postgres views and rules.
One set of tables - one set of views - many independent sites with only one site's data visible to drupal per site.
I'm feeling pretty pleased with myself because I've got it working already. :-)