Défault dedupe rule ? about civicrm-wp-profile-sync HOT 2 CLOSED

@jbonlinea FYI this plugin uses CRM_Core_BAO_UFMatch::synchronizeUFMatch() and therefore it is CiviCRM that performs deduping before inserting a Contact.

I do have a contact with only it's primary email, but he has no user then a user register with the primary email of the above contact (plus extra contact details) Out of the box, a second contact is created.

I just tested this and the User was correctly matched to the Contact with the same email address.

from civicrm-wp-profile-sync.

Hi @christianwach

Thank's for your reply

@jbonlinea FYI this plugin uses CRM_Core_BAO_UFMatch::synchronizeUFMatch() and therefore it is CiviCRM that performs deduping before inserting a Contact.

ok, actually I I already happen to rely on the de-dupe system when creating synced post from forms using the acf part of this module, and I guessed you used civicrm built-in dedupe system rather than building your own,

I do have a contact with only it's primary email, but he has no user then a user register with the primary email of the above contact (plus extra contact details) Out of the box, a second contact is created.

I just tested this and the User was correctly matched to the Contact with the same email address.

yeah well, I fooled myself, I do have the same behavior than what you describe above... Both using wp-login.php or caldera form to create the user.

The fact is that the (test) contacts have been created using caldera form, and had twice the same email, one primary for main email, and one home email, which were both the same address (due to an other form I used to create the contact).
In the case a new contact was created.

Now that this test contacts is "clean" it's all ok.

Sorry for the disturbance

from civicrm-wp-profile-sync.