-
-
Notifications
You must be signed in to change notification settings - Fork 824
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#1436 Do not CC or BCC Contribution invoice #16005
dev/core#1436 Do not CC or BCC Contribution invoice #16005
Conversation
(Standard links)
|
@magnolia61 Can you clarify - is this for an event contribution? |
Yes, I also opened up a gitlab issue to discuss this problem and best solution |
Related to issue: https://lab.civicrm.org/dev/core/issues/1436 and to PR: civicrm/civicrm-core#16005
Betty and I are reviewing PR's and we came across this PR.
@mattwire or @eileenmcnaughton can you merge this PR? And also the docs PR? |
Docs PR is approved for merge-on-release. Please don't merge the docs PR - we'll do this when the change releases (or as close to release as possible!)
|
Thanks guys! |
Overview
Contribution Invoices were send to CC and BCC email adress that were configured only for Event Confirmation purposes.
Opinions and discussion over at: https://lab.civicrm.org/dev/core/issues/1436
Before
When sending an invoice to a user it automatically also got send to the CC and BCC email that were configured for Event Confirmation purposes. While these email addresses are in use to let the event leaders know how many participants can be expected and info on their diet etcetera, it is an unexpected and undesered result when sensitive contribution details (payment arrangements etcetera) are automatically send by CC and BCC to these people.
After
Only the contribution contact gets the contribution invoice.
Technical Details
just removed CC and BCC from the function
Comments
I can understand some organizations would feel the need to have CC of BCC options for the contribution invoice mechanism. If so, that should be coded. But automatically (and non-configurable) send contribution invoices to people not configured to receive these should not happen.