Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Remove sms_incoming_queue_worker()
function. Function was made obsolete by #2677682: SMS message FIFO dispatch queue
Remove sms_incoming.inc
file . This file has not been upgraded to D8, and shouldnt be required due to D8's new router system?
Remove sms_incoming()
function. Refer users of this function to $provider->queue()
.
Remaining usages in SMS Framework:
- 1x sms_devel: SendForm.php
- 1x sms.module sms_incoming_queue_worker - obsolete
- 1x sms_devel: sms_devel_virtualgw_receiver()
Comment | File | Size | Author |
---|---|---|---|
#8 | remove-sms_incoming-2709925-8.patch | 31.67 KB | dpi |
#2 | remove-sms_incoming-2709925.patch | 13.7 KB | dpi |
Comments
Comment #2
dpihttps://github.com/dpi/smsframework/pull/31
Comment #3
dpiWhat are your current opinions on sms.parser.inc, sms_incoming.inc, BootStrapAdminForm?
Its been over a year since they were touched. Is it necessary for SMS Framework to implement a shortcut for gateways, or is the work required for gateways small enough for them to do it on their own?
Comment #4
dpiTagging.
API change and/or schema change.
Comment #5
almaudoh CreditAttribution: almaudoh commentedI was thinking of using a stack middleware to implement the bootstrap functionality, the purpose which was to allow incoming messages to be passed straight to gateways without having to fully bootstrap Drupal.
Comment #6
dpiI havnt looked into such Drupal functions before
Is everything removed in the PR safe? and #2716419: Remove sms.parser.inc ? are we recycling anything?
Comment #7
almaudoh CreditAttribution: almaudoh commentedI've looked at this again, and I think if we ever need this functionality again, it can be easily implemented in D8 with the current capabilities. I don't really know what sms.parser.inc was supposed to parse, but it seems there was this concept of having keyword based mobile-originated SMS receivers and parsers. This is what SMS Actions module is primarily doing - it allows old Drupal 6 / 7 triggers to be defined based on the keywords in a received SMS and then these triggers can be linked to actions.
I will make a meta issue that ties all these bits together.
Comment #8
dpirerolld
Comment #9
dpiHold onto that thought: #2641888: Port SMS Actions to Drupal 8 #comment-11199679
Comment #11
dpi