5

Multi-Site is the way to go http://wiki.civicrm.org/confluence/display/CRMDOC/Multi+Site+Installation With Domain Access you can get into trouble because CiviCRM would expect one domain per "civicrm.settings.php".


4

There is documentation covering setting up multisite CiviCRM on multisite Wordpress here. Additionally, this is an example of the code I put into civicrm.settings.php to set the base URL based on the domain: $multi_site_path = explode("/", $_SERVER[REQUEST_URI]); if ($multi_site_path[6] == "cron.php") { $multi_site_choice = $_GET["site"]; } ...


4

i think you are right that there is not a lot of information about this currently. Multiple language can be enabled on the Localisation screen ie at http://d46.demo.civicrm.org/civicrm/admin/setting/localization?reset=1 Some documentation about it is here http://gitbook.civicrm.org/the-civicrm-community/localising-civicrm.html http://wiki.civicrm.org/...


4

Not sure yet about SE protocol but there are other options than L1 L2 etc especially if there is no requirement to have separate Drupal domains for each component. For example, we have delivered multi-level permissioned solutions using the Related Permissions extension. This can go as many levels deep as required. For example if Org X has permissioned ...


4

Yes - I've done this several times. Many organizations with a chapter/branch format do this, such as IMBA, Wikimedia Foundation, the Australian Green Party, and many others. There are several different approaches you can take. The "easy" approach is just to use built-in ACLs. Create groups of "staff" and "members" for each chapter, using parent/child ...


3

Yes, you can run several independent Drupal sites off the same codebase. Some instructions are here: https://www.drupal.org/documentation/install/multi-site Basically, each has its own database and its own sites/yoursite.org folder where the settings files and site-specific files go. All use the sites/all folder. When you visit via http://yoursite.org, ...


3

As Peter has said, CiviCRM's current support for multiple languages is restricted by the underlying architecture. Basically an extra column is added to the tables for each field that needs to be represented in the additional language. For example if 5 languages are enabled then the table could have 5 times more columns. The issue with this is that mysql has ...


3

This is a bug. Please log an issue on https://issues.civicrm.org.


3

I have a Wordpress multi-site that's working quite well. Note that there are two approaches to Wordpress multi-site: subdomain and subfolder (e.g. "site1.example.org, site2.example.org" vs. "example.org/site1", "example.org/site2". I posted instructions on the wiki page Lobo mentioned for how to set up civicrm.settings.php for subdomain multi-site. I ...


3

It appears that you're using CiviCRM in a multisite configuration. You may want to update this question and future questions to reflect that. Relatively few folks use it, and it affects the answer to this question. In short - you don't normally need a parent group, but with multisite, you do. There's details on why here.


3

Are you using the same payment processor naming for both? You must give it a unique name.


2

It should be vastly superior to run multisite for the very fact you state: "That way people who register for the site will be added to our main Civi user database, rather than keeping track of two separate databases on each website." One of the main benefits of using a CRM is to have a centralized database of all constituent information, be it contacts, ...


2

I don't have time to dig out an example but you should find you can add a Views Filter and specify the civi Domain. May depend on whether your View is starting with the Drupal User or with the CiviCRM Contact.


2

A lighter-weight solution to this (imo) is to use the Permissioned Relationship approach, which can be used to limit User A - who has a Permissioned Relationship to Organisation A - to only access Contacts that Org A has a permissioned relationship over. This deploys very well without the wiring involved in multisite (imo) and hence is more approachable for ...


2

CiviCRM multisite allows you to have several organizations sharing the same instance of CiviCRM, but only a superuser can see the data across all sites. The most common example is an organization with multiple chapters. You mention your organization is active in different countries. If: You require that users from country A not be able to see contacts ...


2

I manage one WordPress multisite instance, so I looked how cron is configured. We use wp-cli with the CiviCRM extension to trigger cron. Cron jobs look like: 11,26,41,56 * * * * /full/path/to/wp-cli --user=civicrmcron --url=https://sitenumber7.org/ --require=/full/path/to/wp-cli/civicrm.php --path=/path/to/wordpress/webroot civicrm api --timezone=America/...


2

All of those settings are set per-site. If you're more comfortable looking at things at the SQL level, you can check out everything stored in civicrm_setting. Note the presence of a domain_id field; each domain ID corresponds to one of the sites (see civicrm_domain to map them). It's pretty safe to use SQL to copy those settings if you need to bulk change ...


2

Well, the answer appears to be 'Yes, it is (almost) that simple'. The one wrinkle is that you first need to trick CiviCRM into thinking it has not already been installed on another Wordpress network site by moving civicrm.settings.php to an out of the way location. So, do this: Move your old civicrm.settings.php file somewhere safe. Create a new empty ...


2

I've seen this happen when there's a permission issue on the version-info-cache.json file that prevents the upgrader from properly deleting it. The file can be found in your CiviCRM "Temporary Files Directory". If you're not sure where to find your Temporary Files Directory, you can check at Administer menu » System Settings » Directories. If there's a ...


2

OK. So I've found what I think is a pretty serious problem with the current Civi CRM setup and multisites... There's an entire section up the top of civicrm.settings.php that has these lines: $civicrm_paths['wp.frontend.base']['url'] = (URL path) $civicrm_paths['wp.backend.base']['url'] = (URL path to admin) $civicrm_setting['URL Preferences']['...


2

So I found the problem. Thanks to @HomoTechsual who lead me in the right direction. The reason had been found in the Settings - Outbound Mail. It was set to mail() with a success message : Your SENDMAIL settings are correct. A test email has been sent to your email address. That looked good but in fact the message was never sent by the server ! Trusting ...


2

I haven't done multisite with Wordpress, but I think this link is more up-to-date documentation: https://docs.civicrm.org/sysadmin/en/latest/install/multi-site/#wordpress-multisites If using a WordPress multisite when CiviCRM is activated the civicrm.settings.php file is added within the uploads directory for that site. Site 1, generally the main site of ...


2

This sounds like a scenario with multiple website but one CiviCRM, and the websites communicating with CiviCRM using the API. Some more information on this kind of scenario on https://civicrm.org/blog/jaapjansma/using-civicrm-form-processor-extension-to-handle-form-submissions-from-an-external and https://docs.civicrm.org/civiproxy/en/latest/


2

==> I found the trouble : that was in the role setting : Multisite: view/edit/list all contacts in domain was not selected for this role… I my case, all the site share same user and roles along the sites. But the actual setting needs to be defined in each site. Therefore the warning was indeed accurate and indicating a wrong setting for the role.


2

Yes - this can be done - you will find instructions on how to integrate Civi with a WordPress Multisite installation HERE. Hope this helps!


2

We totally gave up on using sub-groups with the CiviCRM Multisite. This is too bad but really this seems to be far too complicated and very risky. That would also damage the work of people using different sites. We use only the Domain Group S-group for Site S to be sure we have the right contact in the right site.


2

There are multiple conflicting methods of installing CiviCRM with Drupal 8. It sounds like you're either a) placing the vendor directory into your webroot, or b) symlinking the vendor directory into your webroot. The lack of definitive instructions for D8/Civi is frustrating. However (for security reasons) I believe the community won't accept a solution ...


1

Thanks Jon G, for steering me in the right direction and hopefully this might help someone down the line. I probably wasn't particularly clear in my description in that I run a Drupal multisite but CiviCRM is still running under it's original single site (although this is bringing me a step closer to having all the sites run CiviCRM especially for webform ...


1

You should be able to fix this by defining the CIVICRM_CMSDIR constant. Since you're using multi-site, you'll need to define that on a per-site basis.


1

I would always recommend to have CiviCRM on a separate server from the public facing website (privacy, security and updates) even thought it is more cumbersome and more expensive. So I assume you will have 3 WP websites, and one central CiviCRM (in a dummy Drupal or WP). I would use CiviProxy to ensure only whitelisted API calls are accepted (check https://...


Only top voted, non community-wiki answers of a minimum length are eligible