Closed (duplicate)
Project:
Multiple Email Addresses
Version:
7.x-1.x-dev
Component:
Documentation
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
25 Oct 2011 at 23:10 UTC
Updated:
5 Jun 2016 at 16:07 UTC
Jump to comment: Most recent
Comments
Comment #1
emilorol commentedHi,
This is a quick note, in case someone is looking for a similar solution:
1. I could not the multiple emails module to do this as the phone numbers are not exposed in a token nor there a way to categorize them like business, personal, cell, etc.
2. My solution was to use the profile and create two fields one to collect the phone number and the other a drop down with the list of the text gateways for multiple providers.
3. From there after updating the profiles of the site users I went ahead and I install the "Profile Token" module that makes every profile field a token.
4. Now back in Rules I just have to add one more action to send an arbitrary email and in the "To" field I added the two tokens like [pager]@[provider] and that is it.
5. Now every time a content type X is added to the site the user been referenced is not only notify by email he/she also gets a text message.
Thank you,
Emil
Comment #2
kevinquillen commentedI actually took a different route with Rules support.
In a sense, I added multiple emails as an extended property of the user account. In multiple_email.info.inc (I added to my project), I did the following:
Then, in multiple_email.module, the callback:
This returns a list of emails in the account that are non-primary and are marked confirmed. In my Rules action, I would do 'send a system message', to the user:email, and then loop that list variable, and send an email to them as well. This worked extremely well for me. For example, I have a Commerce order: order confirmation email that is sent to a customer on each checkout completion - the same email is also send to the secondary emails in the account.
Edit: Sorry, I did not notice that this was asked against the 6.x version of Multiple Email.
Comment #3
drummWould be great to see a patch for this. See https://www.drupal.org/patch
The query will need braces,
{}, around the table name.Comment #4
drummComment #5
geek-merlinSee #2742777: Add entity API integration (where the above is already implemented) and #2742851: Add rules hooks.