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 CiviCase (Moderator: Dave Greenberg) »
  • civicase multisite
Pages: [1]

Author Topic: civicase multisite  (Read 663 times)

mhaak

  • I’m new here
  • *
  • Posts: 2
  • Karma: 0
  • CiviCRM version: 3.3
  • CMS version: Drupal 6.20
  • MySQL version: 5.0.82
  • PHP version: 5.2.9
civicase multisite
April 01, 2011, 03:11:46 am
I'm planning a CiviCRM / Drupal deployment and thinking about trying to separate the data and configuration from the code for a multi-site installation.  One of the snags I'm running into is that the CRM/Case/xml/configuration directory is in the CiviCRM root, which means the configuration would affect all sites running that code?  Anyone have any experience with or ideas about how to separate out the config directory from the code so that the config directory can be site-specific while I use the same CiviCRM module for all sites?

mhaak

  • I’m new here
  • *
  • Posts: 2
  • Karma: 0
  • CiviCRM version: 3.3
  • CMS version: Drupal 6.20
  • MySQL version: 5.0.82
  • PHP version: 5.2.9
Re: civicase multisite
April 01, 2011, 03:34:48 am
i was just directed by a colleague to the custom templates field at .../civicrm/admin/setting/path
i will have to test that out
sorry for the extemporaneous post
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviCase (Moderator: Dave Greenberg) »
  • civicase multisite

This forum was archived on 2017-11-26.