CiviCRM Community Forums (archive)

Another multi-site UFMatch problem:

When first setting up a new site under a multi-org installation, initially the only Drupal user will be uid 1. So as this user, you create a new Drupal user. This fires civicrm.module's civicrm_user, which calls the UFMatch code, with the permissions of uid 1. The UFMatch code takes the dedupe route rather than the CRM_Contact_BAO_Contact::matchContactOnEmail route, because $_POST is not empty. So even once the dedupe code is changed to respect ACLs, because here it's operating as uid 1, it will match against all domains and ignore CIVICRM_UNIQ_EMAIL_PER_SITE, as described in the original post.

So the newly created user will be matched to an existing contact in another domain if one exists. This contact will then be a member of both sites' parent groups.

Dave J

Hi Deepak,

Thanks for your comments. I'm not certain but I believe it worked correctly before CRM_Core_BAO_UFMatch::synchronizeUFMatch was changed to use different execution paths depending on whether $_POST is empty. I mean this code, around line 210:

            if ( ! empty( $_POST ) ) {
                $params = $_POST;
                $params['email'] = $uniqId;

                require_once 'CRM/Dedupe/Finder.php';
                $dedupeParams = CRM_Dedupe_Finder::formatParams ( $params      , 'Individual' );
                $ids          = CRM_Dedupe_Finder::dupesByParams( $dedupeParams, 'Individual' );
               
                if ( ! empty( $ids ) ) {
                    $dao = new CRM_Core_DAO( );
                    $dao->contact_id = $ids[0];
                }
            } else {
                require_once 'CRM/Contact/BAO/Contact.php';
                if ( $uf == 'Standalone' ) {
                    $dao =& CRM_Contact_BAO_Contact::matchContactOnOpenId( $uniqId, $ctype );
                } else {
                    $dao =& CRM_Contact_BAO_Contact::matchContactOnEmail( $uniqId, $ctype );
                }
            }

I believe the else clause ($_POST empty) does the right thing: CRM_Contact_BAO_Contact::matchContactOnEmail checks CIVICRM_UNIQ_EMAIL_PER_SITE and if set, it restricts the search to contacts in CRM_Core_BAO_Domain::getChildGroupIds.

So I'm wondering if the solution to all the problems mentioned above is to use the CRM_Contact_BAO_Contact::matchContactOnEmail route rather than the CRM_Dedupe_Finder route for the cases we're discussing. However I don't know the context or intention of the above code, there's probably a good reason why it is as it is. Just had a dig around, seems to be rev 24219 for CRM-5104 (Add ACL Support for CiviReports, Autocomplete contact search widget, and Full-text search).

Dave J

Does this perhaps relate to the issue i just spotted whereby I have two civicrm contacts with the same drupal account?

See http://issues.civicrm.org/jira/browse/CRM-6083

Dave J