2

Solution for Freeform 3: Preventing duplicated field id: Set a custom field id prefix. Using the form handle might be a good id, as long as you're not using the same form twice on the same page. Preventing duplicated form id: Manually adjust the form id parameter to something unique.


2

It’s potentially possible with a custom module, but it would be far less effort (not to mention, more secure) to just apply the solspace form classes to the regular log in form.


2

When you're dealing with that many fields it's definitely a non-trivial undertaking but Craft does have all the tools you need to pull it off. Your plan B is probably the most solid option. Make a new section that houses the skill entries and then set up all the radio buttons on it you'll need. You can put fields on Users directly but it gets weird as they ...


1

This was a separate issue causing this, the above works fine.


1

By default it doesn't add them. You can get that added automatically by adding useRequiredAttribute: true to your form embed tag: https://docs.solspace.com/craft/freeform/v3/template-objects/field.html#properties


1

Broadly speaking, any Form plugin that implements Forms using Elements can probably be used headlessly using Craft's Element API plugin. I'll give an example using the Sprout Forms plugin. Install the Element API plugin Add a config/element-api.php file to your project's config folder Build your API The following example creates two endpoints. The first ...


1

I asked the same question a couple of months back. I was told that it would require some advanced customization to the plugin. It sounded like a pretty big project.


1

It looks like this isn't something that's currently possible. The code that generated the honeypot field isn't able to be extended vendor/solspace/craft-freeform/src/Services/HoneypotService.php::240 I ended up doing some js magic, like this: if(this.formHoneypotName) { let stickyFingers = form.target.querySelector('#' + this.formHoneypotName) ...


1

I managed to get this working in the end. Here is my final code; {# Calculate entries per day #} {% set form = entry.form %} {% set todaysEntriesIndex = 0 %} {% set submissions = craft.freeform.submissions({ form: form.handle }).all() %} {# Count each submission from the day #} {% for submission in submissions %} {% if submission.dateCreated | date(...


1

You could use the regex field (not sure if that is available in the lite edition). In that field you could put in regular expressions to evaluate the data entered and force an error if the evaluation doesn't work. For example you could enter this as the regex patter to prevent a field from accepting special characters and numbers: ^[a-zA-Z\s.-_']+$ Freeform ...


1

Im running into the same issue. In my case they are completely different forms but both with "Enable AJAX" set to true. Could not find anything in the docs either. This is the error I am seeing. I think I have it narrowed down to the honey pot field not being unique per form. Removing the honey pot setting, fixes the issue. [DOM] Found 2 elements with non-...


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