-
-
Notifications
You must be signed in to change notification settings - Fork 825
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
CRM-18713 complete #8628
CRM-18713 complete #8628
Conversation
No point in including it in this if statement.
This is a more comprehensive fix to CRM-18713 that attempts to remove some code that was clearly copied/pasted from the email code.
We need tokens to be properly replace with contact tokens or any other kind of custom token and we shouldn't run any of the token code if no tokens are present in the message. Also, removed non-working code that tried to determine if noSMS is selected.
wanna tackle the style warning fails? |
Yup - thanks for the heads up. white space fixes committed. |
Jenkins re test this please |
I don't understand jenkins error. The error link (https://test.civicrm.org/job/CiviCRM-Core-PR/10317/checkstyleResult/error/) takes me to a page that says: No report files were found. Configuration error? What does that mean? |
Click on console & you get to https://test.civicrm.org/job/CiviCRM-Core-PR/10317/console & in there
|
@civicrm-builder retest this please |
@jmcclelland You say this is an alternative fix to #8626 which has now been merged, so is this PR still relevant? |
I think it is up to core team. This pull requests does important re-factoring and code cleanup so it is still relevant. However, it might not be worth the time needed to QA it. See https://issues.civicrm.org/jira/browse/CRM-18713 for a long discussion about the reasons for this PR. |
test this please |
I'm going to close this - after this long your comment about time to QA it sounds on the money - I suspect at this point it's easier to start from scratch to refactor this as other changes will have happened |
Alternate, more comprehensive fix to CRM-18713. This is an alternative PR to #8626.