Understanding multisite
There are so many different understandings of multisite, and so many different solutions with configuration options, that I wonder if we might make a way of quickly describing them. As I see it multi-site solutions differ mainly on what is shared between sites, and what is unique. Therefore, here is a rough first cut of shared / unique features against a range of solutions. I don't know enough to fill in the boxes - I'm only suggesting a way of notating here.
Each cell is filled in with (S)hared, (U)nique, (E)ither, or (C)omplicated.
| multisite module | groups | Domain Access module | etc. | |
|---|---|---|---|---|
| Users | U | S | C | |
| Vocabularies | U | S | E | |
| Node access | U | E | C | |
| Menus | U | S | S | |
| Themes | E | S | ||
| Database | U | S | S | |
| Architecture | U | S | S |
Then people will be able more quickly to choose which multisite solution is the closest fit for them.
Groups:
Login to post comments
Well..
I like it. For Domain Access, the answers are:
Users: E
Vocabularies: E
Node Access: S
Menus: E
Themes: E
Database: S
Architecture: S
By default, Users, Vocabularies, Menus and Themes are shared, but can be be Unique using the included Domain Prefix and Domain Theme modules.
Not sure I like the term "Complicated" -- it doesn't match the others from a meaning standpoint. It's like saying Apple, Orange, Either, Porcupine.
Add the node access system is default, standard, so I don't think "Complicated" is accurate.
--
http://ken.therickards.com/
http://savannahnow.com/user/2
http://blufftontoday.com/user/3
Vocabularies for Groups
Vocabularies for groups can be shared & unique (See og_vocab).
If you had made this post a wiki page instead of a discussion (story), than several of us could help refine the conclusions.
For the Virtual Site module
For the Virtual Site module the answers are:
Users: S
Vocabularies: S
Node Access: S
Menus: E
Themes: E
Database: S
Architecture: S
Helpful
Thanks Matthew, this is useful. For Groups, I would have thought:
Users: E
Vocabularies: E
Node Access: S
Menus: E
Themes: E
Database: S
Architecture: S
Files
What about having different files for each site, how could that be done, including the upload to the correct sites/www.domain.com/files folder, not just an htaccess to get them back.
Not sure
File handling is a bit complex in Drupal. I was never able to get different files directories working for Domain Access.
--
http://ken.therickards.com/
same for content (view) access controls?
Hi there.
I know my question is not about multisite excuse me for posting it in this group. But this thread is what I'd like to see with a focus on content access instead of per (sub)domain alteration of the site. Despite extensive searching I haven't found anything; I guess I just search with wrong key words. Personally I'm looking for a way to not only control edit, delete, etc. rights as most (core) modules come with but also view rights. I only see "view content" rights but not on a per content type basis.
What I mean is a matrix of access module vs. what kind of access rights it controles and what method it uses. An example module would be taxonomy access.
Cheers.