The attached patch brings the core SMS Framework D7 Rules integration up-to-date for Rules 2.x, including missing hook_rules_data_info() implementation and missing token labels/descriptions.

I also added a simple Rule Action for sending an SMS to a number. This is different than the "send to user" action in the sms_user module, since it sends to a number in any arbitrary entity field as long as it's accessible as a token in Rules. If you combine this with VBO, you can send to any list of SMS numbers you can create with a view (user fields, node fields, etc).

CommentFileSizeAuthor
#4 sms_rules.patch2.45 KBfago
smsframework-D7-RulesImprovements.patch3.12 KBnmcclain
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

BenK’s picture

BenK CreditAttribution: BenK commented

Interesting idea... I'll take a look and test.

fnapo’s picture

fnapo CreditAttribution: fnapo commented

Could you please send more detailed informations on how to send multiple SMSs with VBO on D7? Thanks

rbosscher’s picture

rbosscher CreditAttribution: rbosscher commented

I've made an attempt to updated the rules_send_sms module
1054940#5

fago’s picture

fago
Primary language German
Location Vienna
CreditAttribution: fago commented
FileSize
sms_rules.patch2.45 KB

I've had a look at the patch and
* fixed the access callback
* function prefixes to be all in the sms-namespace
* removed the extra logging as sms_send() already handles it

rbosscher’s picture

rbosscher CreditAttribution: rbosscher commented

Nice ;)

Tested it, seems all ok to me.

fago’s picture

fago
Primary language German
Location Vienna
CreditAttribution: fago commented

any updates on this one?

rbosscher’s picture

rbosscher CreditAttribution: rbosscher commented
Status: Needs review » Reviewed & tested by the community

I used your patch now for the last few weeks, sending out almost 2000 sms using it. I think we can implement this :)

mcpuddin’s picture

mcpuddin CreditAttribution: mcpuddin commented
Status: Reviewed & tested by the community » Fixed

Worked well guys! committed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Richard_1618’s picture

Richard_1618 CreditAttribution: Richard_1618 commented

Any chance for any assistance applying this patch please. I've been trying to run it via the patch manager module and it keeps showing an error message "Unable to find the specified module ... trying anyway."

smsframework?

Richard_1618’s picture

Richard_1618 CreditAttribution: Richard_1618 commented
Status: Closed (fixed) » Active
rbosscher’s picture

rbosscher CreditAttribution: rbosscher commented
Status: Active » Closed (fixed)

Why do you try to patch it? It is has already been committed to the latest dev version.
So reopening this issue for not being able to patch seems a bit unnecessary to me.

if the patch manager module say's it cant find the specified module usually you don't enter the correct short name in the module field of the patch manager node.

  • Commit cc2a5f5 on 7.x-1.x, 8.x-1.x by mcpuddin: 
    Issue #1304276 by nmcclain: D7 support for rules 2.x and adding new rule...
nithinkolekar’s picture

nithinkolekar CreditAttribution: nithinkolekar commented
Issue summary: View changes
Status: Closed (fixed) » Active

I still couldn't find "simple Rule Action for sending an SMS to a number which works with any arbitrary entity field" just like mentioned by OP.

could you please share any other modules/steps required to see this action in VBO?

currently these actions are available in VBO

Change the author of content
Delete item
Delete revision
Execute arbitrary PHP script
Make content sticky
Make content unsticky
Modify entity values
Pass ids as arguments to a page
Promote content to front page
Publish content
Remove content from front page
Save content
Send e-mail
Unpublish content
Unpublish content containing keyword(s)
Update automatic entity labels
Update node alias

almaudoh’s picture

almaudoh CreditAttribution: almaudoh commented
Status: Active » Fixed

This issue was fixed years ago. Please open a new support ticket if this feature is still needed. a specific use-case is not satisfied.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.