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

dev/core#1081 fix for error on contribution detail when using custom data order by without select #14746

Merged
merged 1 commit into from
Jul 7, 2019

Conversation

eileenmcnaughton
Copy link
Contributor

@eileenmcnaughton eileenmcnaughton commented Jul 7, 2019

Overview

Fixes fatal error on contribution detail report when sorting by a custom field that is not selected

Before

Fatal error

After

Report succeeds & is tested

Technical Details

I swept up 4 reports in the test (using an existing dataProvider function) - the contribution summary report failed in Full Group By mode so I added a disable->re-enable to address that

Comments

https://lab.civicrm.org/dev/core/issues/1081

@civibot
Copy link

civibot bot commented Jul 7, 2019

(Standard links)

@civibot civibot bot added the 5.16 label Jul 7, 2019
@eileenmcnaughton
Copy link
Contributor Author

@kcristiano fyi since this is against the rc

@kcristiano
Copy link
Member

@eileenmcnaughton I did a quick r-run after applying the patch on top of 5.16-RC.

I did not see any breakage on the Contribution details report (as that was in the issue). However, I don't see any errors without the patch either.

In any case I'd rather have this in than out and have more time for testing.

@eileenmcnaughton
Copy link
Contributor Author

@kcristiano ok - merging based on that - this does add tests that cover the breakage. Unrelated test fail

@eileenmcnaughton eileenmcnaughton merged commit 4bed4ff into civicrm:5.16 Jul 7, 2019
@eileenmcnaughton eileenmcnaughton deleted the order_report branch July 7, 2019 15:35
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.

3 participants