Skip to content
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

core/issues/64 - In custom searches, column headings are being ignored #12001

Merged
merged 1 commit into from
Apr 19, 2018

Conversation

jitendrapurohit
Copy link
Contributor

@jitendrapurohit jitendrapurohit commented Apr 19, 2018

Overview

Fix for column headers missing from almost all custom searches. Some of them are also missing the entire columns.

Before

Screenshot of Postal mailing custom search.

image

After

image

Technical Details

If $value is not set, getModeValue() will set the default selector to CRM_Contact_Selector which is then considered to display column headers and $sort criteria on the result page.

Comments

Regression from eda34f9#diff-32fdf98c87aec5fc49db16d49ab1fabb


Gitlab issue - https://lab.civicrm.org/dev/core/issues/64

@eileenmcnaughton
Copy link
Contributor

I just tested this & agree I could replicate the bug & that this fixes it - merging

@mattwire FYI - regression from #11600

@mattwire
Copy link
Contributor

mattwire commented May 1, 2018

Right, so this fix is just masking a deeper issue as $taskClassName::getTask() is exactly the same as calling CRM_Contact_Task::getTask().

The issue is actually in CRM_Contact_Form_Search::setModeValues as it's a static and self::$_selectorName changes after being called.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants