3

This could potentially be handled a few different ways... 1. Move the Form Title location Remove the Title from the formatting template and set up your main template loading the form to look something like this: {% set form = craft.freeform.form('myForm') %} {% if showFormTitle %} {{ form.name }} {% endif %} {{ form.render }} 2. Wait for Freeform 3.12 ...


2

I was thinking about this myself, and I found the following 2 articles which I have been going over. It looks like it is quite possible: http://craftsnippets.com/articles/using-template-hooks-in-craft-cms https://docs.solspace.com/craft/freeform/v3/overview/relations.html#overview The 2nd link has a heading for “Relating more than one element” which looks ...


2

In that case, it's likely that Sendmail isn't configured on your new host. You could contact them for help in setting that up, though I'd recommend considering a switch to sending via SMTP/API. There's a bunch of different services out there, many of which have free tiers if you're not sending many emails - SendGrid, Mandrill, Amazon SES are a few options ...


2

It looks like setFormFieldValues() has an optional second parameter related to overriding values... public function setFormFieldValues(array $values, bool $override = true) So, changing... $submission->setFormFieldValues(['customField' => $customFieldValue]); ... to... $submission->setFormFieldValues(['customField' => $customFieldValue], false); ...


2

Currently, the Element Connections feature requires that a Freeform array field be mapped to a Craft field that also accepts an array (e.g. Freeform Checkbox Group to Craft Checkboxes). I've made a note about this for us to revisit in the future though, and potentially add a transformer to handle this kind of mapping. :)


1

Yeh - under Settings -> Spam Settings you'll find Block Keywords: Adding http://* and https://* should work. If you get hit with the same spammers throw their domain in there and it should effectively block 'em. As an aside, the honeypot (and/or) Captcha is pretty effective too since most of the form submissions that contain URLs are garbage.


1

Simple fix. The error was being caused by wrapping the freeform render in tags. Removing these changed the request type and now it works. Ex: It should be: {{ craft.freeform.form("contactForm").render() }} and not <form> {{ craft.freeform.form("contactForm").render() }} </form>


1

Okay I got a response from the Solspace team, mentioning that they dont have this feature. I have made a workaround and build a module for Craft, listening to the "After a submission is submitted" event. This is what I did: Event::on( SubmissionsService::class, SubmissionsService::EVENT_AFTER_SUBMIT, function (SubmitEvent $...


1

It sounds to me like you're running into a collision with Vue's template delimiters vs Twig's, which by default are the same as each other ({{ ... }}). The solution is to change Vue's delimiters to something else when you initialise, like this: const vm = new Vue({ el: '#app', delimiters: ['${', '}'], ... ... }); You'd then need to use ${ ......


1

Welcome to Stack Exchange! Yes, your syntax is wrong - you need to remove the curly brackets around entry.contactForm.handle, and the quotations, and actually get the handle. {{ craft.freeform.form( entry.contactForm.handle, { instructionsBelowField: true } ).render() }} Source: Freeform docs


1

With freeform you can install some demo templates from which you can see how it works: https://docs.solspace.com/craft/freeform/v3/setup/demo-templates.html#installing-the-demo-templates You can also render your form with: {{ craft.freeform.form("formHandle").render() }} Some additional info on that and additional custom formatting can be found ...


1

Sorry for the trouble. This is a known issue and we will have a fix for this available in Freeform 3.10.8 in a few days (February 15-16, 2021). :)


1

Not with Freeform - the fields can only be used once in each form, similar to how fields are used in native Craft elements. I believe Formie allows you to re-use fields.


1

I just realized that I can also use the Craft UI element in the field layout designer to accomplish this. http://craftsnippets.com/articles/using-template-ui-elements-to-extend-craft-cms-control-panel


1

Wouldn't it be smarter to create a new invisible field and add it to the relevant form and then dynamically fill it in with the date in the front-end template. This way you could filter submissions via custom fields. As below: {% set submissions = craft.freeform.submissions({ fieldSearch: { yourDateField: 'now'|date('d M Y') } }) %}


1

Freeform 3, with ajax enabled: <script src="https://code.jquery.com/jquery-3.5.1.js"></script> <script type="text/javascript"> // Find the form element, can be a specific ID or just look for any forms var form = $('form[data-id]'); if (form) { form.on('freeform-render-success', function (event) { ...


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