Jumped right in and managed to get a basic form working quickly. I'm having a problem with the auto-response part though. Originally, I had the field name "email" for a text field element. When I used "[email]" in the auto-response, the person submitting the form would get an error:
"Your form could not be submitted for the following reason(s):
Failed to send an email to "[email]"."
I tried changing the field name to "subscriber" - same error with the new name.
Now, I can't even put a field into the auto-response section. The pulldown menu shows nothing available for the "To:" field. I think this latest issue (no shows) began with the update.
"Your form could not be submitted for the following reason(s):
Failed to send an email to "[email]"."
I tried changing the field name to "subscriber" - same error with the new name.
Now, I can't even put a field into the auto-response section. The pulldown menu shows nothing available for the "To:" field. I think this latest issue (no shows) began with the update.
What you need to do here is edit your form and go into the Settings > Email Notices and for the FROM address, enter an email address that is found on your server. That will fix this error.
~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~
Scott A. Swedorski - VP of Product Development
CoffeeCup Software Inc.
Phone: 678.495.3480
~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~
Scott A. Swedorski - VP of Product Development
CoffeeCup Software Inc.
Phone: 678.495.3480
Thank you, Scott. I'm still having an issue because the "To:" field doesn't have any options when I click the drop-down arrow - it's empty. I have 3 text fields with names, but none are popping up. This wasn't happening (that I noticed) until I upgraded to 1.1.
The error was being generated under 1.0 (when To: fields were showing).
The error was being generated under 1.0 (when To: fields were showing).
Any response on this?
AdamJD wrote:
Any response on this?
Any response on this?
You must add an Email Address Magical Element to your form. ~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~
Scott A. Swedorski - VP of Product Development
CoffeeCup Software Inc.
Phone: 678.495.3480
I have a similar issue, I am using notification message, and the From address shows formname@www.domain.com
I think the www.domain.com may be getting blocked. I want it to always come from info@domain.com
I put the from in the form.cfg.php but it continues to come from formname@www.domain.com
What can i do so the notification message email always comes from always comes from info@domain.com?
I think the www.domain.com may be getting blocked. I want it to always come from info@domain.com
I put the from in the form.cfg.php but it continues to come from formname@www.domain.com
What can i do so the notification message email always comes from always comes from info@domain.com?
Barry Roos wrote:
I have a similar issue, I am using notification message, and the From address shows formname@www.domain.com
I think the www.domain.com may be getting blocked. I want it to always come from info@domain.com
I put the from in the form.cfg.php but it continues to come from formname@www.domain.com
What can i do so the notification message email always comes from always comes from info@domain.com?
I have a similar issue, I am using notification message, and the From address shows formname@www.domain.com
I think the www.domain.com may be getting blocked. I want it to always come from info@domain.com
I put the from in the form.cfg.php but it continues to come from formname@www.domain.com
What can i do so the notification message email always comes from always comes from info@domain.com?
In version 1.2 we will have an option sof this in the software but for now you can manually adjust this setting by editing one of the scripts. You can find instructions here at http://www.coffeecup.com/help/articles/ … m-builder/ ~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~
Scott A. Swedorski - VP of Product Development
CoffeeCup Software Inc.
Phone: 678.495.3480
Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.