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

CRM-18713: ensure SMS activities are sent to all contacts #8479

Closed
wants to merge 1 commit into from

Conversation

jmcclelland
Copy link
Contributor

Only try to fill in details if we have tokens to replace. Otherwise
our array gets populated with all data for the contact and the mobile
number carefully chosen is lost.

https://issues.civicrm.org/jira/browse/CRM-18713

Only try to fill in details if we have tokens to replace. Otherwise
our array gets populated with all data for the contact and the mobile
number carefully chosen is lost.
@joseltorres
Copy link
Contributor

volunteering to review

@joseltorres
Copy link
Contributor

I could not replicate this issue.

I have tested this scenario with civi 4.6 and found that once I chose the drop down to send sms, the correct mobile phone was in the TO box on the compose form. Civi pulled the correct mobile phone although it was not the primary phone number.

It's also my belief that your change could cause additional issues because if (!empty($returnProperties) || !empty($tokens)) would never result in TRUE if the site has no custom tokens. You may want to check an review any custom code that defines any custom tokens. Maybe you can also provide more context, were you using twilio or clickatell? I am also assuming that you're running on civi 4.6 since both twilio and clicktell extensions are not yet compatible with 4.7.

@colemanw
Copy link
Member

colemanw commented Jun 5, 2016

Closing for the moment, feel free to reopen if above questions are addressed.

@colemanw colemanw closed this Jun 5, 2016
@joseltorres
Copy link
Contributor

@jmcclelland once the changes to the PR are made that are mentioned in the JIRA issue, this PR should be good to merge

https://issues.civicrm.org/jira/browse/CRM-18713?focusedCommentId=90024&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-90024

@jmcclelland
Copy link
Contributor Author

New PR: #8527

Thanks!

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