Can't turn off duplicate matching for profile

[samarkand]

I've set up a profile and I don't want CiviCRM to do duplicate matching.

I've left "Update contact on a duplicate match?" unchecked in the profile settings, yet if someone uses the form and enters an email that already exists on the database, then that pre-existing contact is updated rather than a new contact created.

Even if I eliminate all the fields in the "Matching Rules for Individual Contacts," or if I set the weights in every duplicate contact rule so that a matching email is insufficient to attain a matching contact, CiviCRM still considers a pre-existing email to warrant a matching contact, and thus updates the old contact rather than creates a new one. (In testing, I filled in the form using a different computer from what I am logged in with so that there aren't any logged-in-user issues coming into play.)

This problem has (mostly*) been recreated on the CiviCRM demo. A "Halibut Lovers" profile has been set up with the duplicate matching setting unchecked: http://demo.civicrm.org/drupal/civicrm/admin/uf/group?action=update&id=5

The duplicate contact rules are all set so that the weight of a matching email is insufficient to call a matching contact.

The profile form at http://demo.civicrm.org/drupal/civicrm/profile/create?reset=1&gid=5 was filled out using the email address of Jane Demouser (Contact ID#102) but with a different first and last name. Despite the unchecked duplicate matching setting and duplicate contact rules, Jane Demouser was transformed into Arno Salzburg, the first and last names entered on the form.

* This problem was only "mostly" recreated on the demo because I got a "non-recoverable error" when I tried to fill out the form on a different computer from what I was logged in with. The demo seems to only let you fill out a profile form if you are logged in.

[Donald Lobo]

1. Duplicated this on demo and then went to check the code. For some reason that i can't recall, we ALWAYS do a match on email irrespective of the rules. I'll check with kurund and dave and check if they remember why we do this

2. In the profile case, we apply the dupematch rule: http://demo.civicrm.org/drupal/civicrm/admin/dupematch?reset=1. In a 2.x release we will eliminate the inconsistency and apply the same duplicate contact rules in all cases

3. I could successfully create/update records using that profile as anonymous. Not sure why u are getting a fatal error

lobo

[samarkand]

The purpose of the profile was to collect signatures for an online petition. The contact information of the signers needs to be contained (at least for the time being), and not have any intermixing with existing contact records because the information as submitted to the object of the petition should be exactly as entered in the profile.

Also, if duplicate matching cannot be completely disabled for profiles, it seems this opens up the database to the possibility of vandalism. Someone who has partial information on an existing contact could enter that into the profile, along with bogus information, and trigger a duplicate match with the existing contact record being updated with false information. Maybe that's unlikely to happen, but I'd prefer to eyeball the profile data before integrating it with the rest of the contacts.

As for automatic duplicate matching on finding the same email address: some people share email addresses with a partner.

Thanks for your help.