Unexpected behaviour: Adv Search not searching non-primary emails

[petednz]

Hi - was surprised to find that Adv Search does not search non-primary email address - maybe there is a setting - will check - but if it doesn't (and I think it should) then the description "Complete OR partial Email Address" should state 'primary only'. Or have I hit a bug - or am is something else amiss. Thanks

[Chris Burgess]

Can verify this and another unexpected behaviour with regard to non-primary email addresses which I tested this morning on CiviCRM 2.2

• I created a contact with primary email "primary@example.com" and secondary email "secondary@example.com"
• I searched my contact DB for contacts with email "secondary@example.com" using the Advanced and Basic Search forms, and CiviCRM reports "No matches found". (This is the issue Pete reports above.)

I think that CiviCRM should show matches for non-primary email addresses when using Advanced Search (unless the user searching instructs otherwise). I've opened an issue on this: http://issues.civicrm.org/jira/browse/CRM-4287

A related issue:

• After adding the above contact, I added a new Drupal user via Drupal's admin interface with login "secondary" and email address "secondary@example.com". The new Drupal user was created as expected.
• When I edit the Drupal user, their Drupal email has been changed to "primary@example.com"
• I removed the user "secondary" and created another user with the email "secondary@example.com" through Drupal's registration process. The result was the same (and Drupal sent its notification email to "primary@example.com").

If CiviCRM should be changing the email address assigned by an administrator to a Drupal user, then we need to notify the person creating the account of the change by alerting them to the fact that the supplied email address has not been used.

However, this may not help if the user no longer has access to an email address listed as their primary address, so I've opened an issue on this in JIRA: http://issues.civicrm.org/jira/browse/CRM-4288

[petednz]

There was also the issue that if a person has no email in 'primary location' but has in 'other location' then Drupal just throws a wobbly as it can't do the substitution outlined by Chris and basically rejects the attempt to create a user account

[Chris Burgess]

Pete, can you document the process for this? Preferably using less jargon than "throw a wobbly", which is clearly a technical term I don't quite follow

I just added a new contact with a phone number in their primary location, and email "secondary@example.org" in a secondary location. I then successfully added a Drupal user with a matching email address.

In this case it seems the absence of a primary email address didn't cause a problem, and CiviCRM did successfully match the Contact and Drupal user based on the email address.

Searching for the email address in CiviCRM returns no matches, so it seems that the email is considered "secondary" by CiviCRM.

[petednz]

Possibly I have merged two of the issues I hit last night. So the wobble may be entirely mine. I recall I hit onen where I could not create a User as it was not accepting the email address - yet I could not find the email address when I ran a search. But you have disproven my first theory so will try and cook up another one.