CiviCRM Community Forums (archive)

Hello everyone,

As part of an international organisation we are trying to implement a website that caters for all of our National Offices around the world, allowing them to store and maintain contact records. Currently the website has a sub domain for each country. e.g.

fr.alpha.org for France
uk.alpha.org for United Kingdom

The website has one code base for drupal and CiviCRM, but has a diffferent CiviCRM database for each subdomain. The reason that we are using a seperate databases and not the domain ID solution for each country is data protection, so that no one country can access anothers data. We would like a system where a generic user that registers through a user record in drupal, on fr.alpha.org is only added as a contact record in the french civicrm database. Currently CiviCRM Role Sync will create a new record in every database where there isn't one already.


A potential solution would be......

1) Identify the users country of origin at registration and store against their profile using a field in drupal. This field will be hidden in the registration form and populated from the first portion of the URL...

Field: profile_default_country
Values: 0,uk,fr (to match URLs)
Type: multi select drop down

This could be an array so that a user could access more than one database if necessary...for example admin users.

- a form alter hook in a custom module can be used to automatically populate the field at registration and then an admin could add to the array to provide access to other countries CiviCRM databases.

2) Update the synchronize function to check the users default_country against the current domain and only sync the user if they match

- this function lives in civicrm/CRM/Core/BAO/UFMatch.php

3) Civi profile data will only be accessible on the users native site - to ensure users only edit their profile on their native site, we need to remove the edit link on their profile if they are accessing from another version.
 - a hook_user in a custom module can be used to implement this.

4) CMS admins would be able to assign a user to 2 or more default languages by editing their profile and selecting multiple default countries.

Does anyone have anymore potential ideas or know of any reasons why this wouldn't work?

Thank you very much for your time!!