Download & Extend

Multiple email address for an option in the Options field?

Project:Webform
Version:6.x-2.7
Component:Code
Category:feature request
Priority:normal
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

I have defined a field called "Reason for Inquiry" which currently looks like this:

one@example.com|Select 1
two@example.com|Select 2
three@example.com|Select 3

But I want a given option to be able to send to more than one email address like so:

one@example.com,also-one@example.com|Select 1
two@example.com|Select 2
three@example.com|Select 3

I get the email to one of the email addresses, but not both. Is this feature supported? Can it be?

Thanks! Great module - very handy!

Comments

#1

#2

Status:closed (duplicate)» active

I don't see this as a duplicate key issue as the "#282436: Multiple Options, Same Value in 'Select' Form Element" is addressing. I have unique keys, but my issue is I have multiple email addresses for each option. Or maybe I am missing something? If so, can you point that out? Thanks.

#3

Category:support request» bug report

Sorry for the haste in marking duplicate. With 300+ issues at all times, it's difficult to keep on top of them. I thought this should work, as comma-separated e-mail addresses works fine when placed in the standard E-mail recipient field. But as you report, it seems that only one e-mail is sent out to one of the addresses. I'll move this in the bug queue, though I won't have time to investigate it further in the immediate future.

#4

Thanks much! I appreciate your work on this module - it's a very good module.

#5

Category:bug report» feature request

Well, okay I looked at this again and realized if this were implemented it could easily turn your site into a spam machine (well, up to 255 characters of e-mail addresses at a time). It would allow the end-user to enter many e-mail addresses into a single field, and then all of them would receive e-mails. Right now Webform is specifically designed to prevent such unintentional mass-emailing.

This wouldn't be a bad problem is specifically applied to select lists (where Drupal prevents the end-user from tinkering with the entered values). However I'm not interested in implementing this as a built-in feature. You can accomplish a similar goal by using the Additional Validation field, see the Webform Handbook for some examples.

#6

Status:active» closed (won't fix)

As described above, this is not planned on being added.

#7

Version:6.x-2.3» 6.x-2.7
Status:closed (won't fix)» active

According to a comment in the documentation it works to separate the email addresses by commas.
http://drupal.org/node/273806#comment-1845060

Would it be possible to clarify what is working and what is not working?

#8

Status:active» fixed

This feature actually *was* implemented as part of #284487: filter_xss incorrectly called on array?, and has been available since the 2.4 version.

#9

Status:fixed» closed (fixed)

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