Hi,

congratulations for this module.

I have a few questions about it maybe someone can help me. Thanks in advanced.

I have installed the module, it's ok.

When a new site 'test' is created:

1.- it creates the tables test_* that is OK, but only the 40 tables for a drupal basic installation, not the 75 tables that I have, so, where and what I have to modify to create the tables that I need for all the modules I have installed.

2.- I have modified the http.conf adding the lines for the virtualhost. I also see the settings.php help in the multisite manager administration. The code for this settings.php must be placed :

a) inside sites/default/settings.php
b) inside a new file sites/site/settings.php
c) other -> where?

3.- when the site is created does it creates the folder 'test' under drupal/sites/site or under drupal/sites with a settings.php ? Do I have to do it manually or it's supposed that with the settings.php (point 2) is not necessary?

If I do not need clean url then that's all? did I forgot something?

Thanks again

Comments

schuyler1d’s picture

schuyler1d commented
Status: Active » Fixed

1.- it creates the tables test_* that is OK, but only the 40 tables for a drupal basic installation, not the 75 tables that I have, so, where and what I have to modify to create the tables that I need for all the modules I have installed.
Multisite Manager does not install a 'copy' of the main site, but a fresh instance. Any extra modules, etc. that you want added should be put into the drupal/profiles directory (edit the default version or copy it to make your own). If it's specific modules you want added on initial installation, then that should be easy (just add those module names to the top of the default.profile)

2.- I have modified the http.conf adding the lines for the virtualhost. I also see the settings.php help in the multisite manager administration. The code for this settings.php must be placed :
b) inside a new file sites/site/settings.php
This is the closest, however if you have domain example.com, then you want it to be called sites/com.site/settings.php, because drupal needs some part of the domain in the directory name.

3.- when the site is created does it creates the folder 'test' under drupal/sites/site or under drupal/sites with a settings.php ? Do I have to do it manually or it's supposed that with the settings.php (point 2) is not necessary?
You need to do that manually. It would be a big security hole if your web account had write access to your drupal/sites directory.

Glad you like the module, and let me know if you have any other issues/questions. Your confusion should probably be fixed by better documentation. If you have specific suggestions in that regard, please send them along.

paulowsky’s picture

paulowsky commented

Hi again,

thanks for your answer, also for the speed.

3.- when the site is created does it creates the folder 'test' under drupal/sites/site or under drupal/sites with a settings.php ? Do I have to do it manually or it's supposed that with the settings.php (point 2) is not necessary?
You need to do that manually.

Ok but where drupal/sites/site or under drupal/sites?

It would be a big security hole if your web account had write access to your drupal/sites directory.

Ok, I understand, can you imagine if it would be possible to do it thought another way? MySql trigger? Cron job that reads the drupal_site table and creates the folder when there is a site created? any other way?

One more thing, as the way you have create this module with the Virtualhost configuration I understand (maybe I'm wrong) that it should not be necessary to reboot the apache after a site is created (no matter if we do the folder 'site' manually or automatically).
Correct ?

Thanks again for your support and your time.

schuyler1d’s picture

schuyler1d commented

Ah, I see the confusion.

The point of the special settings.php code is that you have a SINGLE settings.php for ALL your sub-sites. Once you have setup the single drupal/sites/com.site/ directory, all subsites with the url http://example.com/site/* use that directory. So when I said that code goes into drupal/sites/site, I didn't mean drupal/sites/{site} ('site' is not a wild card).

WRT VirtualHost, any changes in httpd.conf will require an apache reboot. However, there's an easier way to do this, if you are on unix--simply:

$ cd drupal
$ ln -s . site

If you're not using clean URLs then you don't need to change the .htaccess or virtualhost settings at all.

paulowsky’s picture

paulowsky commented

Ok, I see, now I understand how it works.

You have help me a lot !!!.

That's all by my side, this issue can be closed.

Thank you very much.

Paul

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.