Answers.Body: <p>Answer to first question: There is an extension that allows one to seaech for any telephone or email by location: <a href="https://github.com/JMAConsulting/biz.jmaconsulting.search.anyteloremail" rel="nofollow noreferrer">https://github.com/JMAConsulting/biz.jmaconsulting.search.anyteloremail</a></p>
  
  <p>My guess is that it should still work even though it is only marked as working for 4.5 and 4.4. Please open an issue in github repo if there is a problem and we will update it. To have this search ability added to core searches, I'd recommend getting agreement after opening a gitlab issue.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-10T22:07:27.490Z
Answers.Text: I haven't yet heard a use case for always excluding a non-primary email from a search result.  Is there any reason this useful extension (assuming it works with 5.6+) couldn't be a core merge?
Answers.UserDisplayName: CiviTeacher
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-11T16:26:12.373Z
Answers.Text: Sometimes people want to send only to home or only to office or only to billing, regardless of which is primary. If this were to go into core, I'd suggest refactoring code so that functionality is present in Advanced Search somehow. I suppose it could be added to Search > Custom Search easily. But 5 years ago or more when I reviewed those searches for Lobo most had significant problems and he was iirc thinking of removing the whole area. In any event, dgg and lobo at the time didn't want to add it.
Answers.UserDisplayName: Joe Murray
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-09T21:30:43.000Z
Answers.LastActivityDate: 2018-10-09T21:30:43.000Z
Answers.UserDisplayName: Joe Murray
Body: <p>Two longstanding inconvenient issues about the search:</p>
  
  <ol>
  <li><p>it does not locate non-primary emails (see attached)</p></li>
  <li><p>if you fail to place a space between the lastname, firstname it will not return any results</p></li>
  </ol>
  
  <p>The feedback I get from users (particularly new ones) is that this is quite flummoxing, while experienced users tend to overlook this as "the way it has been" and not see it as a problem.</p>
  
  <p><a href="https://i.sstatic.net/j85Ii.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/j85Ii.png" alt="enter image description here"></a>
  <a href="https://i.sstatic.net/XFUnV.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/XFUnV.png" alt="enter image description here"></a>
  <a href="https://i.sstatic.net/Gz4Ss.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/Gz4Ss.png" alt="enter image description here"></a>
  <a href="https://i.sstatic.net/iAlRw.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/iAlRw.png" alt="enter image description here"></a></p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-10-05T23:40:33.873Z
Comments.Text: There is a solution for non-primary: https://civicrm.stackexchange.com/questions/11125/is-there-anyway-to-search-on-a-non-primary-email-address/11152#11152
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-10-09T21:31:17.040Z
Comments.Text: Note that stackexchange format works best when there is only one question per 'question'. Could you revise by creating a second question, maybe providing links to cross reference?
Comments.UserDisplayName: Joe Murray
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-10-10T22:04:51.277Z
Comments.Text: The purpose of my post is to meet the requirement for Josh's new "feature requests" GitLab forum, in which he requests we post here first.  So I'm confused as to what to do to help others help others, and fear I have only created a mess.  But at least the idea is out there now.  ;-)
Comments.UserDisplayName: CiviTeacher
Tags: <search><primary>
Title: Feature request: Make search more forgiving and spaces after comma and non-primary emails
ThreadText: # Feature request: Make search more forgiving and spaces after comma and non-primary emails
  
  (Asked by: username_0 on 2018-10-05)
  
  Two longstanding inconvenient issues about the search:
  
  1. it does not locate non-primary emails (see attached)
  2. if you fail to place a space between the lastname, firstname it will not return any results
  
  The feedback I get from users (particularly new ones) is that this is quite flummoxing, while experienced users tend to overlook this as "the way it has been" and not see it as a problem.
  
  [![enter image description here](https://i.sstatic.net/j85Ii.png)](https://i.sstatic.net/j85Ii.png)
  [![enter image description here](https://i.sstatic.net/XFUnV.png)](https://i.sstatic.net/XFUnV.png)
  [![enter image description here](https://i.sstatic.net/Gz4Ss.png)](https://i.sstatic.net/Gz4Ss.png)
  [![enter image description here](https://i.sstatic.net/iAlRw.png)](https://i.sstatic.net/iAlRw.png)
  
  **Tags:** search, primary
  
  > **Comments:**
  > **username_1**: There is a solution for non-primary: https://civicrm.stackexchange.com/questions/11125/is-there-anyway-to-search-on-a-non-primary-email-address/11152#11152  
  > **username_2**: Note that stackexchange format works best when there is only one question per 'question'. Could you revise by creating a second question, maybe providing links to cross reference?  
  > **username_0**: The purpose of my post is to meet the requirement for Josh's new "feature requests" GitLab forum, in which he requests we post here first.  So I'm confused as to what to do to help others help others, and fear I have only created a mess.  But at least the idea is out there now.  ;-)  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2018-10-09. Score: 1
  
  Answer to first question: There is an extension that allows one to seaech for any telephone or email by location: <https://github.com/JMAConsulting/biz.jmaconsulting.search.anyteloremail>
  
  My guess is that it should still work even though it is only marked as working for 4.5 and 4.4. Please open an issue in github repo if there is a problem and we will update it. To have this search ability added to core searches, I'd recommend getting agreement after opening a gitlab issue.
  
  > **Comments:**
  > **username_0**: I haven't yet heard a use case for always excluding a non-primary email from a search result.  Is there any reason this useful extension (assuming it works with 5.6+) couldn't be a core merge?  
  > **username_2**: Sometimes people want to send only to home or only to office or only to billing, regardless of which is primary. If this were to go into core, I'd suggest refactoring code so that functionality is present in Advanced Search somehow. I suppose it could be added to Search > Custom Search easily. But 5 years ago or more when I reviewed those searches for Lobo most had significant problems and he was iirc thinking of removing the whole area. In any event, dgg and lobo at the time didn't want to add it.  
  
  ---
  
  