CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using Multi-Site functionality »
  • shared preferences settings for 'n-drupal 1-civicrm' multisite - clarification
Pages: [1]

Author Topic: shared preferences settings for 'n-drupal 1-civicrm' multisite - clarification  (Read 2416 times)

Michael McAndrew

  • Forum Godess / God
  • I live on this forum
  • *****
  • Posts: 1274
  • Karma: 55
    • Third Sector Design
  • CiviCRM version: various
  • CMS version: Nearly always Drupal
  • MySQL version: 5.5
  • PHP version: 5.3
shared preferences settings for 'n-drupal 1-civicrm' multisite - clarification
May 18, 2011, 07:29:29 am
Hello,

Just want to get some clarification on preferences, settings, etc. for "n-drupals, 1-civicrm multisites"

It looks like nearly all preferences are shared in civicrm_domain.config_backend (and it seems reasonable that this should be the case).

One obvious exception is info in civicrm/admin/domain which changes based on the domain.  Are there any other settings / preferences that are not shared?

Michael
Service providers: Grow your business, build your reputation and support CiviCRM. Become a partner today

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: shared preferences settings for 'n-drupal 1-civicrm' multisite - clarification
May 18, 2011, 10:29:26 am

it depends on the domain id setup in the below.

if you use the same db and same domain id in the civicrm.settings.php for the n drupal sites then everything is shared

if you use the same db and different domain id in the civicrm.settings.php for the n drupal sites then everything is shared then a few things are not shared. Easiest way to find which ones is by checking the schema and seeing while tables have a domain_id

the goal this time around was to limit the tables that have it, so we could do it with ACL's (and hence flexibility). However when working with GMVCO on this it seemed to be getting towards a slippery slope and GMVCO switched to using individual sites for each client (they also underestimated how much each client was willing to share)
 
lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

Eileen

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4195
  • Karma: 218
    • Fuzion
Re: shared preferences settings for 'n-drupal 1-civicrm' multisite - clarification
May 18, 2011, 07:39:48 pm
not shared if you use different domain ids include:

payment processors
membership types
default currency
custom paths
Make today the day you step up to support CiviCRM and all the amazing organisations that are using it to improve our world - http://civicrm.org/contribute

chiebert

  • I post occasionally
  • **
  • Posts: 50
  • Karma: 1
  • CiviCRM version: 4.3
  • CMS version: Drupal 7
  • MySQL version: 5.1
  • PHP version: 5.3
Re: shared preferences settings for 'n-drupal 1-civicrm' multisite - clarification
March 07, 2012, 08:43:53 am
Quote from: Eileen on May 18, 2011, 07:39:48 pm
not shared if you use different domain ids include:

payment processors
membership types
default currency
custom paths


Eileen: is this still the case? I can confirm that default currency and custom paths are segregated, but I'm seeing all payment processors and membership types in both domain contexts, even though their domain_id values are correctly differentiated in the database. I'm going to try a re-install from scratch just to be sure... (civi 4.1.1, Drupal 7.12)

Eileen

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4195
  • Karma: 218
    • Fuzion
Re: shared preferences settings for 'n-drupal 1-civicrm' multisite - clarification
March 07, 2012, 11:29:01 am
Actually, I submitted a fix in JIRA the other day to only show payment processors (and report instances) on their correct domain. It will be in 4.1.2.

I didn't look at membership types.

I did have a conversation with Dgg & Kurund about restricting membership statuses by domain id (a request from a customer) or more generically by membership type. But no concrete plans in place for this.
Make today the day you step up to support CiviCRM and all the amazing organisations that are using it to improve our world - http://civicrm.org/contribute

chiebert

  • I post occasionally
  • **
  • Posts: 50
  • Karma: 1
  • CiviCRM version: 4.3
  • CMS version: Drupal 7
  • MySQL version: 5.1
  • PHP version: 5.3
Re: shared preferences settings for 'n-drupal 1-civicrm' multisite - clarification
March 07, 2012, 11:33:59 am
Thanks, Eileen - that'll be a helpful update. Fortunately it's not a critical need for the client right now, since they can use the same processors. The memberships restrictions would be helpful, but with care we'll get around it for now.

Eileen

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4195
  • Karma: 218
    • Fuzion
Re: shared preferences settings for 'n-drupal 1-civicrm' multisite - clarification
March 07, 2012, 12:00:51 pm
Just to clarify - membership types, processors, report instances are per domain BUT there is a bug (fixed for the second two in 4.1.2) where the admin pages don't discriminate by domain.
Make today the day you step up to support CiviCRM and all the amazing organisations that are using it to improve our world - http://civicrm.org/contribute
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using Multi-Site functionality »
  • shared preferences settings for 'n-drupal 1-civicrm' multisite - clarification

This forum was archived on 2017-11-26.