We had a need to store the recipient phone number in the message options instead of pulling it from a user entity. The attached patch updates the SMS Queue Processor to allow for this technique to be used.

CommentFileSizeAuthor
#2 3203755-smsframework-2.x-dev-recipient-options.patch805 bytesattheshow
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

attheshow created an issue. See original summary.

attheshow’s picture

attheshow CreditAttribution: attheshow at Richland Library commented
FileSize
3203755-smsframework-2.x-dev-recipient-options.patch805 bytes
dpi’s picture

dpi
Location Perth, Australia
CreditAttribution: dpi as a volunteer commented
Status: Active » Postponed (maintainer needs more info)

Looking at the patch, I don’t see what the point is? It’s pulling the recipient and adding it back again?

Can I ask for the an example use case of the consuming code?

attheshow’s picture

attheshow CreditAttribution: attheshow at Richland Library commented

Yeah, so if the module providing the gateway needs to store the recipient's phone number in the database for later processing by the queue, but isn't targeting a user entity as the source of recipient contact information, this is an alternate way to store and retrieve that information.