-
-
Notifications
You must be signed in to change notification settings - Fork 828
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
Fix fatal error when sorting by status in activity search #15923
Conversation
(Standard links)
|
@eileenmcnaughton i think test failures may relate here |
441f527
to
941ce95
Compare
test this plese |
@eileenmcnaughton did some |
Also: Thanks for picking this up! |
I managed to resolve the issue and also remove the confusion a little by doing the following
|
941ce95
to
f4401a2
Compare
@seamuslee001 I pushed up al alternate |
@eileenmcnaughton this is now generating fatal errors for me like
|
f4401a2
to
26896d8
Compare
@eileenmcnaughton looks like something has gone wrong in the rebase here |
26896d8
to
6b05131
Compare
@seamuslee001 hopefully right now |
I have just r-runed this and confirmed that the sorting works and also both search builders work merging |
Overview
Alternate fix to #15911
Technical Details
This leverages the CRM_Core_DAO::appendPseudoConstantsToFields function (as does Contribution Search) which adds the metadata in a standardised way. It switches to referencing the $key rather than the name as $fields is keyed by uniqueNames & in the case of activity_status_id that is not the same as the field name