Virtual Sites - duplicate module?

scedwar - March 6, 2008 - 02:50
Project:Virtual Sites
Version:6.x-1.x-dev
Component:Miscellaneous
Category:support request
Priority:normal
Assigned:Unassigned
Status:closed
Description

There are numerous solutions to the multisite problem and I'm just wondering what this module brings that other solutions don't already? I posed this same question a little while ago and got a very useful thread, containing links to some *very* detailed discussions and case studies: http://drupal.org/node/212915
Can you explain how this fits into those discussions?

I'd also add that from what I've seen of the domain module http://drupal.org/project/domain we already have a well developed solution (with a 6.0 port well in progress). Perhaps you could join forces to develop some of the missing domain contrib modules?

#1

skirr@drupal.ru - March 12, 2008 - 19:06

Looks like its works differently and dont conflict with other node access modules and dont need any core patches.

really want to hear the answer on this:

There are numerous solutions to the multisite problem and I'm just wondering what this module brings that other solutions don't already? I posed this same question a little while ago and got a very useful thread, containing links to some *very* detailed discussions and case studies: http://drupal.org/node/212915
Can you explain how this fits into those discussions?

#2

fokke - March 13, 2008 - 16:55

(removed: duplicate post)

#3

fokke - March 13, 2008 - 16:54
Status:active» closed

It works very different.

  • My approach is really just cosmetic. It overrides basic subsite-related things like theme, theme settings, menu's, site information. No rights, seperate content, table prefixen etc.
  • On the other hand it is more flexible since it uses the Condition module. A subsite is not restricted to a subdomain, but could be only one page. Or event to a role, which takes it far away from the multi-site idea and more into like conditional formatting/settings/themeing of your site for specific area.

#4

scedwar - March 13, 2008 - 18:32

Can you confirm that this is 6 only?

It would be useful if you could add some discussion to the thread I referenced as this looks like a solution that would work for many. What is interesting about the various multisite solutions is that they all have pros and cons and each have their own use cases that would favour them. For my particular purpose, domain is better, but I would certainly see cases for this.

In fact, the 'multisite' solutions run all the way from very simple changes in theme elements such as blocks, through to sections (a module that may be superseded by virtual sites?) that applies themes to site sections, through to taxonomy solutions that start to break the site up into subsites, domain that provides access permissions etc in one table with multiple domains and themes/menus etc, through to the traditional multisite solutions that may not even share a db or code.

I think this topic is really begging for somebody with more knowledge and understanding than I have to do a round up, maybe a handbook section/comparison.

#5

christefano - March 21, 2008 - 05:25

@scedwar: there's a comparison of a few of the multisite solutions at http://groups.drupal.org/node/9796. I hope that when a comparison is found in the handbook that it comes out of that discussion.

 
 

Drupal is a registered trademark of Dries Buytaert.