The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.
By madhusker on
[edit: moving to post installation forum.]
Hi,
Using the site wide contact form module supplied with drupal core will not allow more than one email address. Below the email box in setup it states you can separate multiple addresses with a comma. "Example: 'webmaster@example.com' or 'sales@example.com,support@example.com'. To specify multiple recipients, separate each e-mail address with a comma."
One email works fine but more than one fails to send to either party. Any ideas? I couldn't find any info in the forums.
# cat contact.info
; $Id: contact.info,v 1.3 2006/11/21 20:55:34 dries Exp $
name = Contact
description = Enables the use of both personal and site-wide contact forms.
package = Core - optional
version = VERSION
; Information added by drupal.org packaging script on 2007-01-30
version = "5.1"
project = "drupal"
Comments
Bump.. Anyone?
Bump.. Anyone?
Where do the devs live that
Where do the devs live that maintain drupal core?
=-=
in IRC, core developers don't visit the forum very often especially when working on a next core version.
have you tried adding a space after the , ?
Yes, it parses the space
Yes, it parses the space after you save it. Then it fails to work because it thinks it is a single address. Here is what is in the logs:
Error sending email: "SMTP Error: The following recipients failed: "foo1@domain1.com,foo2@domain2.com" From: "sender@somewhere.com" To: "foo1@domain1.com,foo2@domain2.com".
It seems this was broken along the way and we should fix it or remove the feature. I would like to keep it as I need to contact more than one person for things like membership. What is the next step? Can a bug be filed somewhere?
Thanks.
=-=
yes, use the "Issues" link in your navigation menu and navigate the drop down menus to file a bug against Drupal, contact.module
no love
This is the only thing I don't like about drupal. I wish the core got some debug attention.
=-=
I beg to differ, if bugs are reported properly then they do indeed get "love" & attention. Reporting a bug in the forums has a tendency to be overlooked. you can file issue on core modules using the issues link in your navigation menu. issues -> create : then navigate to Drupal: contact module using the drop down menus.
It was reported 7/16/07 and
It was reported 7/16/07 and still unassigned. I know they are heavily focused on a new release (and that's good) but there has to be a little attention when it comes to a core problem in the version marked stable. If I could fix it myself I certainly would. Somewhere along the line this was broken and just getting core functionality back would be good for everyone. It could even be as simple as a single line of code that was overlooked in the new version.
http://drupal.org/node/159925
Fixed at last!
I just upgraded to 6.4 and the bug has been resolved. Looks like from the post many months later it was fixed in a newer version even though it was unassigned.
http://drupal.org/node/159925