Multi Site

I am working on two projects at Cornell that might benefit from sharing one Drupal code base. The obvious options include:

1. Common Drupal code / shared database (using Domain Access)
2. Common Drupal code / separate databases (using Multi-site)

My questions:

• Does anyone have a recommendation about which approach is easier to maintain?
• Does the second option with separate databases make it easier to develop the multiple sites on separate time schedules?

Craig

I'm not sure if this is simple question or not, but I'm a little bit confused.

I am planning on developing 4 drupal sites that are essentially pretty much the same in terms of what they do, they will look different but will more or less do exactly the same job as each other with the odd exception. What I'd like to know is if it is possible to feed the sites from the same database and most importantly can the sites share the same cck fields 'if and when' they are required, or do you need to either share all fields or non at all?

Hello,

I need your help for a tricky use-case with the Domain Module:

I use D7 with Domain to create a site with multiple regional subsites (www.domain.com/germany, www.domain.com/austria, etc). A part of the content is shared, some other content is per-site and foreign content should not be seen nor be editable from another regional admin. Everything is multi-lingual, regional language and english. The domain module makes all this possible in a sleek way that almost made me wet my pants. There is just one problem:

I can define the domains using subdomains or actual domains:

I set up a staging server for a multi site and it seemed that is was working fine. I then install the blog module as use1. I had no problems. when I tried to give an authorize user access the select boxes looked good. after submitting the page I looked and the box we empty (not changed.)

Perms on the files and directories all seem right and match the production site.
checked node access and reentered the code, no difference.

on the staging site a new install was done the sites directory was copied from production.