Virtual Sites module
Has anyone tried the Virtual Sites module? I'd be interested to hear a comparison between using this module and the various multisite techniques people are already using.
Groups:
Login to post commentsGroups.drupal.org is a part of the drupal.org group of sites. Logging in on this site requires an account on the main drupal.org site. If you do not have an account on drupal.org, you will need to create one, log in over there, and then come back here where you should automaticall
Thanks!
Does what it says on the box
All content is in one space / one database, you can just override various things based on the incoming domain. All these different solutions are hella confusing for anyone trying to figure out when to use one over the other. e.g. virtual sites says "no FTP or SSH required!" -- which, for me, isn't really a bonus :P
Virtual site
I need to create three website
eg:www.web1.com
www.web2.com
www.web3.com
i need this three website will have entire different look ,with different menus and data content. But i need to use single database.
So i installed conditions and virtual sie. But i am not sure how to do with virtual sites. Please give me some information about it.
Interesting
Sounds very similar to http://drupal.org/project/domain -- which, at least, I think more clearly describes what it does. I wonder why this project was written -- what use-case it solves.
What I do not see, looking at the code, is how the module partitions content across the various virtual sites.
[ Update: Apparently, it does not, see http://drupal.org/node/230563 ]
The more interesting piece for me is the new Condition(s) module: http://drupal.org/project/condition
@Boris -- see also http://groups.drupal.org/node/9796
--
http://ken.therickards.com/
http://savannahnow.com/user/2
http://blufftontoday.com/user/3
I gather that a virtual site
I gather that a virtual site made with Virtual Sites is something more along the lines of what I've thought subsites or microsites were.
Thanks for the link to http://groups.drupal.org/node/9796. I hope that when a comparison of the various multisite solutions is found in the handbook that it comes out of that discussion.
Virtual site
I need to create three website
eg:www.web1.com
www.web2.com
www.web3.com
i need this three website will have entire different look ,with different menus and data content. But i need to use single database.
So i installed conditions and virtual sie. But i am not sure how to do with virtual sites. Please give me some information about it.
Thinking more
I believe that Virtual Sites expects you to use its hooks to separate content using table prefixing. So the fundamental difference between VS and Domain is that Domain is designed to selectively share content across a collection of sites.
--
http://ken.therickards.com/
http://savannahnow.com/user/2
http://blufftontoday.com/user/3
Thinking over the Virtual Site and Domain Access
Hi agentrickard,
I've been following the discussion about Virtual Sites and Domain Access which I think have 2 very different ways of reflecting a multisite architecture.
I have tried out the domain module which is really great and I am thankful for that. It defeats most of the issues related to multi-site on multiple domains. In my case I have the exact same requirements as it is described in the use case but for subsites in subfolders.
I'd like to know if it could be possible to use subsites not as subdomains, but rather as a single domain with several small sites in a "folder-like" architecture.
For example in a multi-user blog system, the urls would be:
example_blog.com
example_blog.com/user1
example_blog.com/user2
example_blog.com/user3
Each one of these would be a site which could use the different modules and rules defined in the domain access module.
The "global home" (in this case example_blog.com） could aggregate articles from different sub-blogs.
Maybe it's just impossible to do so with the current domain module but it can be customized to work as I suggest. Otherwise if I'm mistaken could you give me some new tracks for the way to go?
Please let me know what you think would be the best option in order to achieve this kind of architecture.
Cheers, David.
Well...
The Domain User module tried to do this, but slightly differently. It would give you:
example_blog.com
user1.example_blog.com
user2.example_blog.com
user3.example_blog.com
I do not know how the module would behave with different subfolders -- that is not how it was designed -- and I do not quite see the benefit to that approach, which is kind of how Drupal behaves now.
See also the new Subdomain module, which does the above without the node access overhead of DA.
--
http://ken.therickards.com/
http://savannahnow.com/user/2
http://blufftontoday.com/user/3
DOmain Module
Hey agentrickard,
I know I can use domain module for multisite in form of subdomain. Do u have any possible leads for situation like
www.example.com/site1
www.example.com/site2
www.example.com/site3
with site1 , site2 and site3 have different themes and different exclusive manager of respective sites with one single root administrator.
If not possible with current status then do u think is feasible to extend it to accomodate the above requirement.
Thanks,
n4drupal
Where should I start?
I have to start fresh. Part of me wants to do things right the first time. Another part is afraid of starting out too complex for a beginner by doing that. But either way, I have to reinstall drupal on my development server at home, on the one hand, and think about whether to go with multisite on my server, on the other.
First about the reinstall: I originally botched this by first installing xAmpp when I was doing a joomla tutorial, then overwriting that install with a Developer Suite Community Version install, which conflicted with it. At this point, I've managed to delete all related files by uninstalling both. But I've noticed that the DevSide Suite comes with Drupal 5.3 (according to http://drupal.org/node/195238 ).
Well, so do I go with the latest stable release (6.12, I think as of this writing), or are there compelling reasons to stick with a 5.x version?
Second, about multi-sites. On this I have a slew of questions, probably all stupid ones born of my non-experience with CMS generally, on the one hand, and lack of practice working with a development server, on the other.
Well, those are some starter questions. Pretty much everything around here leaves me with more questions than answers. But it certainly sounds like it has some potential if I can catch on.
James Carvin
Thank you for your help!
Using it
I'm running two web sites and I need not to share theme, blocks, user and some node.
I firstly tried prefixing tables like variable, cache, menu, blocks etc, but upgrading modules/code would be too complicated because of db modifications.
I tried then Domain module but it is still a beta and the installation is also too complicated (I don't like the use of "include" and patches) even if, of course, it is a good mdule and hope to see it grow.
At the end I installed Virtual Sites and it seems what I need, stable release, easy to install and flexible as it depends not only on HTTP_HOST but on Conditions (this give me more possibilities like having a Virtual Site dedicated to a particular Role and much more). Blocks are shared so I configure each theme with its own blocks.
About node sharing I added a Vocabulary "Site visibility" for nodes, to filter Views results.
VIRTUAL SITE
Hi,
I need to create three website
eg:
www.web1.com
www.web2.com
www.web3.com
i need this three website will have entire different look ,with different menus and data content. But i need to use single database.
So i installed conditions and virtual sie. But i am not sure how to do with virtual sites. Please give me some information about it.