CiviCRM Community Forums (archive)

I have a number of sites on one server but don't want to use one CiviCRM database as they won't be sharing the same data.

Is this possible?  If so, are there guidelines I can follow?

Have found install for N sites with one CiviCRM database.

So far attempts to set this up in D7 with latest version of CiviCRM just displays "page not found".

Step 1: Clean install of Drupal 7
Step 2: Install of CiviCRM

Many thanks
Jenifer

Yes I have a Drupal multisite setup and followed the install procedure for CiviCRM. 

Yes I do.

Sites defaault directory contains:
     civicrm.settings.php
     default.settings.php
     settings.php

Yes civiCRM is enabled and I've been using it.  Will disabling it cause data loss?

I'm having a similar problem:

Multi-site install, Drupal 7, latest version of Civicrm.

Drupal and Civicrm are installed and working perfectly on one site (the main site). 

We set up a multi-site install (the primary site has a Drupal and Civicrm database, and I set up separate Drupal and Civicrm databases for the second site).

Drupal is working on the second domain (located in the "sites" directory).

When I enable Civicrm (which is already installed because it's sharing the codebase with the primary site), I get the following error:

Initialization Error

Array
(
    [callback] => Array
        (
           

• => CRM_Core_Error
[1] => simpleHandler
        )

   

Code: [Select]

=> -18
    [message] => DB Error: no such table
    [mode] => 16
    [debug_info] => SELECT *,  config_backend, locales, locale_custom_strings 
 FROM civicrm_domain
 
 WHERE (  civicrm_domain.id = 1 ) 
 
 
 
 [nativecode=1146 ** Table 'vsource4_edboost_civicrm.civicrm_domain' doesn't exist]
    [type] => DB_Error
    [user_info] => SELECT *,  config_backend, locales, locale_custom_strings 
 FROM civicrm_domain
 
 WHERE (  civicrm_domain.id = 1 )  [/quote]

I know that the database exists, I can see it in my control panel.  And, I copied the civicrm.settings.php file from the other site and just changed the domain name.  I think I must have skipped a step.

Is there something I need to do to initialize the database? 

I'm following instructions here: http://wiki.civicrm.org/confluence/display/CRMDOC40/CiviCRM+for+Drupal+-+Configure+Multi-site+Installations#CiviCRMforDrupal-ConfigureMulti-siteInstallations-Multi-siteInstallationOptions

Thanks for any help!

The directions on the Wiki were a little unclear.  It read to me as if I could just put the settings.civicrm.php file in the new sites's directory, enable the module, which already showed up, and it would work. 

Well that can work for a multi-org install (which is different than multisite). Which wiki page is this?

This made me nervous, as I was worried that it might erase data that I had on the main installation on the main site.  It did not.  I just set up the new install (from the installation page) and pointed it to the new drupal and civicrm databases that I had created. 

Interesting--you are not the only person with this concern. The installer will never erase data actually. Perhaps we should add a note to that effect...

Yes, I see what you mean. In a nutshell:

Drupal multi-site (in the simplest implementation) means that you have sites/cat.com and sites/dog.com and each has a unique settings.php and a unique database and the sites are unique, except that they share the same Drupal codebase. To add CiviCRM to such a setup, you can do what you did, i.e. by visiting each of these separately:

http://dog.com/sites/all/modules/civicrm/install/index.php
http://cat.com/sites/all/modules/civicrm/install/index.php

and that will most probably install CiviCRM correctly into each of sites/cat.com and sites/dog.com and each would need a unique database. This means that the CiviCRM data of cats has no connection to any of the data about dogs.

CiviCRM multi-org means you start off with a Drupal multi-site as above, and then install CiviCRM into cat.com, but then for dog.com, you don't install CiviCRM. You copy civicrm.settings.php from sites/cat.com to sites/dog.com and then you edit that new file which is sites/dog.com/civicrm.settings.php and you change the directories, meaning the lines starting with

$civicrm_root = ...
define( 'CIVICRM_TEMPLATE_COMPILEDIR', ...
You adjust those to refer to sites/dog.com instead of sites/cat.com. Then you edit the line starting:

define( 'CIVICRM_UF_BASEURL'   
And then you just enable CiviCRM from the regular Drupal modules page. So now you have two unique sites that both connect to the same CiviCRM database. This will cause problems if you stop there, however.

Now you must enable and define the multiorg settings. Those are steps 1, 2, 6, 8, 9 here: http://wiki.civicrm.org/confluence/display/CRMDOC41/Multi+Site+Installation

I'm not sure if step 3 is necessary or not.

I see now that you were looking at a different page, which is more outdated than the page I just posted.

Anyhow, have a look at these and let me know what you think.

I would be happy to take a crack at trying to clarify the wiki -- but certainly don't want to muck around anywhere I'm not qualified to be!  Please let me know if it would be useful for me to try.

Yes, that would be great. We are always happy for more people to become involved. This I think is a perfect way for you to contribute--I believe you have a background in education.

I see what you mean. Seems to me the best would be to take the existing page in the 4.1 space http://wiki.civicrm.org/confluence/display/CRMDOC41/Multi+Site+Installation and rewrite it to give an overview of the different options (as that 4.0 page has) and then details (as much as you have) for how to setup each.

I would say just do it as you feel is logical. Perhaps subpages for the options, or just make one big page and we can also look at it after and see if subpages are warranted.

> Or -- is there a wiki on how to write on the wiki? 

Not that I know of.

> I know that there are strict guidelines for coding.

That's for coding. Here it's for documentation and I don't think we have much in the way of guidelines.

The main thing is to make it as clear as possible for users to read and understand.