9

It can be many reason for this - first needs to check if domain or Server IP (can be for shared hosting) was not blacklisted. Then check email header - you will have a whole picture if any spam flags here, servers ip, from what server is come etc. For example your email can failed DomainKeys (DKIM) test. What I usually do, is setup mail setting for using ...


6

The recipient_email field accepts encoded recipient email values (see an example here), using the {freeform:recipient_value} variable in the field's name="" attribute along with a set list of recipients using recipient1="", recipient2="", etc parameters. If you want your field's value="" to be an regular, non-encoded email address (as you have it above), ...


6

These posts gave me the hints I needed. For others it seems they may have to change email_newline and email_crlf to "\r\n" in your config/bootstrap. CodeIgniter has a smtp_crypto config that can be either ssl or tls. I needed tls to work with AmazonSES. The actual config used by EE is email_smtp_crypto (same for port, docs say smtp_port but in the source ...


6

You don't have to use the {freeform:submit} variable. You could use <input type="submit" /> and style it with CSS to use a background image. Or use <button type="submit"><img src="mybutton.png" /></button> Or <input type="image" src="mybutton.png" />


5

Yes, if you replace {composer:field_output} with {freeform:field:{composer:field_name} attr:placeholder="Your Name"} in the Composer Template. If you're using the Freeform channel custom field (i.e. using the field in {exp:channel:entries}), you'll have to select your custom Composer Template (containing the above code) in the top left dropdown of the ...


5

The problem lies in that you can upload multiple files using FreeForms File Upload Field Type - so you can't just use name="file1" as your field name. To make this work, you have to pass the field type as a post array, so name="file[0]" for the first file (and if you have multiple files name="file[1]", name="file[2]" and so on. So, the resolution (for me ...


5

Unfortunately there is not - when Secure Forms is enabled, EE requires every POST to contain a valid XID. More and more I'm just disabling Secure Forms on any site which takes user submissions because it brings so many headaches.


5

This issue involves the changed security module within EE. Solspace are working on the proper solution however I have also advised them on how to fix this issue (in a different module, facebook connect). To help them and the community, try this: Identify the action used to submit the freeform (refer to the exp_actions) table. Modify the action in ...


4

For our FreeForm forms, we use the following code: {if freeform:captcha} {freeform:captcha}<input type="text" name="captcha" style="width:140px;" /> {/if}


4

You could have a text field named 'chosen_recipients and use a jQuery listener to wait for click of the checkboxes and concat the name results in the hidden field. The hidden field could then be output as a normal field in the notification. <input name="chosen_recipients" type="hidden" /> <script type="text/javascript"> ...


4

When using the Pages module, the URL Title is not used and should not be fed to to the {exp:channel:entries} tag. If you remove that parameter from the tag and change dynamic="yes" or remove the dynamic parameter altogether, it will pick up the correct page entry automatically. You'll also need to make sure the entry with the Page URI set has the correct ...


4

Have you looked at Ben's fantastic LogMeIn add-on? http://devot-ee.com/add-ons/logmein It'll automatically login a member, after you've defined a custom member group & directory for the anonymous visitor.


4

After more investigation, I reviewed the settings for the upload field. Once I checked this previously unnecessary option, the problem disappeared. Disable XSS Clean This option allows you to disable system XSS cleaning just for this file upload field in case you are having issues with user uploads being incorrectly blocked. While I can't be sure, and ...


4

Freeform 4.1.3 is not compatible with EE 2.8. Solspace are working on an update. Adjusting csft_exempt to 1 in the exp_actions table (Freeform - save_form ) got rid of the error so it looks like this has been caused by the security model issue.


4

The {exp:freeform:form} tag is a convenient way to render the form's markup - but because you're dealing with {freeform:field:name} instead of raw HTML it doesn't give you that much control over the markup. However there's a trick so that you can add additional attributes to a field in FreeForm. Simply change your field to this {freeform:field:name attr:...


4

Using SendGrid or Mandrill are great suggestions. Using Escort can help make that an easy process. If you don't want to go that route you might also want to look into creating an SPF record wherever you are hosting your DNS for this domain name. That helps identify which mail servers are allowed to send email from a specific domain. There are a few wizards ...


4

You can add "attr:type" to specify the type of the input field. {freeform:field:email attr:type="email" attr:class="email-class" attr:placeholder="Please fill in your email address" } You can add any attribute you like. Just use it like attr:name-of-attribute="value of attribute"


4

Yes, you can customize the errors given by Solspace freeform. Please see below code to modify the errors. freeform:field_errors {if freeform:field_errors} <h2>There were some error(s) with your submission:</h2> <ul> {if freeform:error:first_name} <li><b>First Name</b> is required.</li> {/if} ...


3

It sounds as though you did not get all the files uploaded correctly. Try deleting the /system/expressionengine/third_party/freeform and /themes/third_party/freeform folders and upload them again from scratch. What version of EE?


3

I might be missing the goal here (you mentioned a plugin so this might be too simple), but you can very easily add a jQuery UI Datepicker widget to any custom form field in Freeform Pro. Just create a custom text field in the Freeform Pro control panel, lets call it Start Date: Field Type: text Field Label: Start Date Auto-generated Field Name: start_date ...


3

A few things to look at here; Do they route their email through a different server to the web traffic? i.e. Do they have an MX record set up for their domain. If so, does that same MX record exist for the server currently hosting the site? I see this from time to time with some sites I host where the client has their email handled elsewhere (say by a mail ...


3

The following is partly taken from the Freeform troubleshooting guide, but here is a list of items to verify when email isn't being sent: Verify that your email address(es) is(are) correct. Check the spam folder of your email account Try sending email using the Communicate Tool in the CP? (CP => Tools => Communicate) Review your template tag parameters ...


3

For now, Freeform is not compatible with EE2.7 - check the blogpost here http://www.solspace.com/blog/entry/compatibility_with_ee_2.7.0/


3

You could do this by using the inline_error_return="" parameter: http://www.solspace.com/docs/freeform/form/#inline_error_return For example, you could craft a special URL when inline errors are encountered, eg: return="template_group/template/errors_found" Then, in your template, use a simple conditional to display your "has errors" message: {if ...


3

fond the issue, when using an index.html file as a site offline page causes the form to now work. Removing the index.html and making the site live with the index.php file allowed the form to work


3

Yes - the fields will export in the order they appear in the admin. Click the "Edit Field Layout" button to control which fields are shown/hidden, and drag them into the order you want them to appear.


3

It was ALL ME! I hate it when operator error is the case! In my general preferences, the name of my sites homepage was set to index.php instead of /. My bad! This was definitely an unnecessary post!


3

Best way to do this is to add the class to a containing element like this: <div {if composer:field_required}class="required"{/if}> <label></label> <input> </div> Then target the input field with css like this: .required input { border: 1px solid red; } You can also use this for your "* required" copy... Change ...


3

collection="" isn't a parameter on the exp:freeform:entries tag in Freeform 4.x. You use form_name="" or form_id="" instead. Take a read through the Freeform 3.x to 4.x Guide as tags/parameters have changed.


Only top voted, non community-wiki answers of a minimum length are eligible