1.) Is there a way to add a Pull down menu option for the subject and have that posted as the subject in the email? Kind website feedback, Feature request, etc as a subject?
<p><label for="subject">Subject</label>
<select name="subject">
<option value="Website feedback">Website feedback</option>
<option value="Support request">Support request</option>
<option value="Feature request">Feature request</option>
</select></p>
2.) Is there a way to get the result email sent showing the person’s name and email address as the sender instead of the CMSs registered email address?
Also in the email I get the subject just has the RE: but no subject in the body of the email it’s looking for a <code>[+subject+]</code> ?Did you set the &subject parameter in the snippet call? mind you in your case the answer to your first question should solve that anyway.
The placeholders are ’targets’ for eForm to fill with data, while the snippet call is a source to supply eFrom with data. I don’t know if you ever could use these placeholders in the snippet call.. Where would eForm get the data from? The eForm placeholders are used in the report, autotext and report template and (generated by the form parser) in the form template.
&from needs one or more regular email addresses, while &fromname expects a real name. You can leave them empty in which case they will be filled with the ’email sender’ and the ’site name’ as set in the MODx configuration.
<form method="post" action="[~[*id*]~]">
<input type="hidden" name="formid" value="feedbackForm">
<label accesskey="n" for="Name">Your Name</label>
<input type="text" name="Name" maxlength="60" eform="Your Name::1><br>
<br>
<label accesskey="e" for="email">Your Email Address</label>
<input type="text" name="email" size="40" maxlength="40" eform="Your Email Address:email:1"><br>
<br>
<label for="subject">Subject</label>
<select name="subject">
<option value="Website feedback">Website feedback</option>
<option value="Support request">Support request</option>
<option value="Feature request">Feature request</option>
</select>
<br>
<label accesskey="c" for="comments">Comments</label>
<textarea cols="40" rows="10" name="comments" eform="Comments:html:1"></textarea><br>
<br>
Please enter the anti spam code below:<br>
<img src="[+verimageurl+]" alt="verification code" border="1">
<br>
<label accesskey="c" for="vericode">code</label>
<input type="text" name="vericode" size="20">
<br>
<input type="submit" name="submit" value="Send Feedback"><br>
<span style="color:#900;">[+validationmessage+]</span><br>
<br>
</form>
Well that’s a little embarassing. I thought I upgraded and I hadn’t... All is well, thank you TobyL
Version 1.3 certainly supports multiple textareas, some earlier version didn’t. Did you download 1.3?
As you can see the submit button and i moved the error code below the submit button are both below and behind my footer so you can’t seem them and I don’t know why? Any thoughts? I’m using the Animetor-Metal template that Susan made and helped me tweak I just can’t figure out why it’s doing that here is my form code:
MODX Staff
Quote from: TobyL at Sep 29, 2006, 11:19 PM
The placeholders are ’targets’ for eForm to fill with data, while the snippet call is a source to supply eFrom with data. I don’t know if you ever could use these placeholders in the snippet call.. Where would eForm get the data from? The eForm placeholders are used in the report, autotext and report template and (generated by the form parser) in the form template.
&from needs one or more regular email addresses, while &fromname expects a real name. You can leave them empty in which case they will be filled with the ’email sender’ and the ’site name’ as set in the MODx configuration.
Hmmm, yeah, what you say makes sense. It’s just that the [+name+], [+email+] and [+subject+] placeholders did work as call parameters in version 1.2.... and [+subject+] can still be used as such... guess I got a little confused
This discussion is closed to further replies. Keep calm and carry on.