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/mailing#56 dev/mailing#57 Ensure that we don't pass in any namesp… #15779

Merged
merged 1 commit into from
Nov 8, 2019

Conversation

seamuslee001
Copy link
Contributor

…aced fields when building the row array for mailing reports

Overview

Following the datepicker conversion for some mailing smart groups, some mailing job fields started to be name spaced which then lead to e-notices of undefined property as per dev/mailing#57 and mailing reports showing incorrect information dev/mailing#56

This resolves it by using the name key for the fields as that will be the non unique / non name spaced version

Before

unique field name used causing e-notices

After

non unique field name used

ping @eileenmcnaughton @totten @demeritcowboy

…aced fields when building the row array for mailing reports
@civibot civibot bot added the 5.20 label Nov 8, 2019
@civibot
Copy link

civibot bot commented Nov 8, 2019

(Standard links)

@seamuslee001
Copy link
Contributor Author

I tested this on the Australian Greens dev and confirmed the issue as per the screenshot below

Before Patch

After applying the patch the report looked correct

after patch

@eileenmcnaughton
Copy link
Contributor

This makes sense but feels kinda hacky - any chance you could follow up with a test against master?

Adding MOP

@seamuslee001 seamuslee001 merged commit 3d46dfb into civicrm:5.20 Nov 8, 2019
@seamuslee001 seamuslee001 deleted the dev_mailing_56 branch November 8, 2019 22:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants