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

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

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

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

When updating freeform, you need to delete the old directories before uploading the new: Updating: Within your sites ./system/expressionengine/third_party/ directory, delete the freeform folder and upload the new one from the /system/expressionengine/third_party/ directory in your download package. Within your sites ./themes/third_party/ directory, delete ...


3

If you're going to be using a form submission to track your project requests all the way through and updating status along the way, I'd think the channel form would be the way to go. With Freeform Pro, you can't really do any editing from the front-end after the initial form is submitted. Users of the control panel can definitely access the form submissions ...


3

Try this parameter to see if it has any effect. status="*" It might be preventing entries with a status of "pending" which is the default from being shown.


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

Not sure this approach is going to work. FreeForm expects you to define recipient1 and recipient2 as a parameter of the exp:freeform:form tag, they are then encoded on the server side and the html source only shows a hashed value for the recipient, not the value you are inserting dynamically. If the method you described here were to be permitted then it ...


3

<input type="text" id="email" name="{email}"/> This is why - you're posting an item whose key is an email address. EE treats this as malicious data (as it contains the @ character). What you meant to write was: <input type="text" id="email" name="email" value="{email}" /> Same goes for all your other inputs - you have name confused with value,...


3

I received the form expired error message using Freeform 4.2.2 and EE 2.9.2. I added this to config.php: $config['disable_csrf_protection'] = "y"; The form submitted, but I really didn't want to leave that setting there. I did a little more digging and found that I needed to add a CSRF Token to my form. So I added this hidden input within my freeform tags: ...


3

It turns out the answer is to turn off "Allow HTML" for all Freeform notification templates. I believe this is because Freeform will then leave the email as plain text allowing Postmaster to encapsulate it as HTML. Benek, I'm glad it's all sorted for you! :-)


3

The only thing come to my mind is adding input:hidden field to your form named(return) then use some JavaScript/Jquery code to change this value depend on checkboxes values. Regard's.


3

I've had to do similar things in the past. Generally what I do is set the return to template_group/template/%%entry_id%% Then, within that template, I use the {exp:freeform:entries} tag to pull up the new entry from the the URL. Within the tag pair, I use conditionals on whatever fields, or something do a custom plugin to handle the logic, and redirect to ...


3

Wrap your {exp:freeform:form} with an {exp:freeform:entries} tag pair and use conditionals to determine if there are more than less than 40 entries for the form. If there are less, present the form, if not, show a message: {exp:freeform:entries /* your other parameters */} {if freeform:no_results} {exp:freeform:form /* your other parameters */} ...


3

I'd suggest doing this via an extension - your best bet is likely to use the freeform_module_insert_end hook, with one extra form input. So in your form, add a hidden input so the extension knows the url_title: <input type="hidden" name="channel_entry_url_title" value="{url_title}" /> This is untested, but it should work: public function ...


3

Change the lines {if freeform:error:{composer:field_name}} <strong> Error: {freeform:error:{composer:field_name}} </strong>{/if} TO {if "{freeform:error:{composer:field_name}}" != ""} <strong> Error: {freeform:...


3

This should work: Add the Freeform field tag: {freeform:field:file} to your form and choose the directory you wish the files to be uploaded to. Go to your notification settings in Freeform and add the {file} tag inside (swap file for your file field name). Make sure the Include Attachments checkbox is unticked and hit save. Now when you get notifications ...


3

You can create your own custom Composer Templates in Freeform, which allows you to pass parameters and variables similar to if you used {exp:freeform:form} or {exp:freeform:composer} in a template. In the Freeform CP. Go to "Composer Templates" and create a new template. Under Template Params, you can add parameters, such as an id or class to your form: ...


3

Low Search doesnt work, Free Form doesnt work, Free members - basically asks if your sure you want to login as some things might not be secure. These add-ons usually use what you have configured in your "Admin > General Configuration > URL to the root directory of your site". You can also set/override the General Configuration settings using the /system/...


3

The more recent versions of EE (I think > 2.7) use CSRF in their forms by default so you automatically get a time sensitive submitted page. If you want to be more explicit and if the above doesn't work for you (i.e. earlier version of EE), I would add a hidden form field (which Freeform allows) and auto-populate it with a unique value - either a timestamp (...


3

Freeform has built in duplicate detection. https://solspace.com/legacy_docs/freeform-4/form/#prevent_duplicate_on


3

This is a known issue with Freeform 5.1.1 (and earlier) and EE 3.4.5+. This issue has since been fixed in Freeform 5.1.2 :)


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