-
-
Notifications
You must be signed in to change notification settings - Fork 825
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CRM-21634 Standardise search fields as they relate to contacts #11492
Conversation
f9dae51
to
7546161
Compare
Jenkins re test this please |
test this please |
7546161
to
a044038
Compare
CRM/Member/Form/Search.php
Outdated
* @return string | ||
*/ | ||
protected function getContactTypeLabel() { | ||
return ts('Participant Contact Type'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@eileenmcnaughton this needs to be changed to member
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah yes, opps
|
a044038
to
0573fd2
Compare
@seamuslee001 I fixed the line you pointed out & am adding merge on pass per your review |
ping @monishdeb @colemanw |
test this please |
1 similar comment
test this please |
civicrm#11492 Bug: 184496 Change-Id: Id7edd36e043a7a3ce0f693a53da6d05af746747d
Overview
Standardise the fields available on different component searches (e.g tags is only available on Contribute, add to Member, Pledge & Participant). I only touched searches Participant, Contribute, Pledge & Member to keep scope manageable.
Before
After
Technical Details
I have increased the shared code component between these searches.
Comments
It would probably be easy to do this for some of the other searches but others have some extra complexity so have kept to the 'core four'. Also formatting inconsistency between searches is odd but pre-dates this