Dear Drupalers, I have successfully performed multi site installation, but have some issues, for which I could not find solutions in previously opened topics.
My multi site installation's structure is as follows:
mainsite.com
/sites/default
/sites/all
/sites/mainsite.com
/sites/sub.mainsite.com
/sites/another.com
I have several questions regarding the above stated structure.
1. Do I need default directory at all? I have deleted it and the structure still works.
2. Where I should put system modules - in sites/all/module directory or should leave them under main directory - mainsite.com's public_html directory? (I have Unix)
3. My sub.mainsite.com works perfectly, but another.com makes some troubles. I have simlinked and properly installed both of them according to the instructions for multi-site installations. Another.com is linked to /sites/another.com and correctly sees modules under /sites/all, but does not want to see system modules either under main directory or under sites/all/modules directory. So I had to put copies of system modules under /sites/another.com/modules. But in this case another.com/update.php does not want to work - shows empty page.
Apparently, in multi site installations subdomains work without problems, but probably binding of completely another domain should be done differently. I could not figure out how and would appreciate very much if someone could point out to me.
Thank you for attention!
Comments
Some answers
1) Its okay to delete it, it's just a fallback if your web servers virtualhost doesn't match any other directory under sites/.
2) If more than one of your sites shares the module, stick it under /sites/all/module - never put modules you download or write in to the core /modules directory.
3) Sounds a bit messed up. We run several different domains and sub domains all from one Drupal installation without issues. I'm not sure what you are doing with your symlinks.... most of the time you would not need them.
just point all your apache virtualhosts documentroot to the same drupal installation directory.
then under sites/ directory create directories to match the servername setting in each of your apache virtualhosts. (you've probably already done this). don't use symlinks...
--
Ixis (UK) providing Drupal consultancy and Drupal theme design.
--
Ixis (UK): Drupal support, Drupal hosting.
budda, thank you for your
budda, thank you for your reply.
2) i actually meant core modules, not contributed. should i leave core module in the main directory (public_html) or should i move them to sites/all/modules?
3) in unix command line i went to /home/another and linked it to /home/mainsite/public_html using a code like
ln -s /home/mainsite/public_htmland works: when i type http://www.another.com in a browser it gets information from /home/mainsite/public_html/sites/another.comwhat did you mean by "just point all your apache virtualhosts documentroot to the same drupal installation directory"? how i "point them to" if not a way that i used and explained above?
it seems other people also
it seems other people also have troubles with update.php in multisite installations: http://drupal.org/node/62394
could my problem #3 be in
could my problem #3 be in the fact that my another.com was previously separate standalone Drupal website? I have just copied all the necessary files to new mutlisite installation and simlinked old public_html directory to my new mainsite with m/s.