Thank you, Petr, for the kind words and the recommendation!

Hi William, thanks for the review, and sorry for the very late reply. I'm answering here mostly for anyone who runs into the same problem.

If a submission appears in the log but no e-mail arrives, the form works and the problem is e-mail delivery:

1. In the form's Recipients tab, replace the demo address admin@domain.tld with your own.
2. On the Details tab, set Sender email to an address on your domain, or leave it empty to use the mail settings default.
3. Configure Settings → Mail Configuration and send a test from Settings → Mail Templates. Errors are listed in Settings → Event Log.

If it still doesn't work, please open an issue at GitHub.

Hi Jess, thanks for the review, and sorry for the very late reply. I'm answering mostly for anyone with the same question.

The partials/renderform/fields.htm override is gone in current versions. Each form now has its own Custom Template tab. Leave it empty to use the generated markup, or write your own layout and render each field by its name:

<div class="row">
    <div class="col-6">{{ form_field('first_name') }}</div>
    <div class="col-6">{{ form_field('last_name') }}</div>
</div>

So contact-form and subscribe-form can each have a different layout. To change the HTML of a field type for every form, edit it under Form Builder → Field types. It's best to duplicate a type first and edit the copy.

If you need more help, please open an issue at GitHub.

Hi Martijn, thanks for the review!

resetForm lives in the plugin's form.js, which the component adds to the page through {% scripts %}. This error means the layout doesn't output it. Make sure the layout contains:

{% framework extras %}
{% scripts %}

More details in this issue.

Thank you, Danny, glad to hear it works well for you!

Hi Julian, you're right, and I'm sorry. Support back then was far too slow.

This has changed since. Every report now goes through GitHub Issues, where I answer and track it. The plugin is actively maintained for October CMS 4. The latest release, 5.2.0, adds security fixes, new languages and reworked documentation.

If you ever give it another try, I'd be glad to help.

Thank you, Remko! Hope the project went well. If anything comes up, you'll find help on GitHub Issues.

Thank you, Jacek! Duplicating a form is available: use the copy button in the Actions column of the forms list. Since version 5.2.0 the copy also keeps the RainLab Translate translations.

Hi Morten, sorry for the trouble. The installation error was caused by a change in the October version released at that time and was fixed in version 1.5.0. Current versions install cleanly on October CMS 4.

If you run into any problem, please report it on GitHub Issues and I'll help you there.

Hi Auris, you're right, plugin:refresh is no fix for a production site, and I'm sorry for the trouble. The installation error was caused by a change in the October version released at that time and was fixed in version 1.5.0, so no refresh is needed. Current versions install and update cleanly on October CMS 4 with php artisan october:migrate.

If you run into any problem, please report it on GitHub Issues and I'll help you there.

Hi Igor, thanks for the suggestion! It's done: the Recipients tab now has repeaters for To, CC and BCC with no limit on the number of addresses, and since version 5.2.0 the submission log stores recipient lists of any length. The plugin is actively maintained again, now for October CMS 4.

Sorry for the disappointing experience back then. Support has changed since: every report now goes through GitHub Issues, where I answer and track it, and the plugin is actively maintained for October CMS 4. If you ever give it another try, I'd be glad to help.

Спасибо за отзыв! Кстати, начиная с версии 5.2.0 плагин полностью переведён на русский язык.

Thank you, Ronny! This is built in now: every submission is stored in the database under Form Builder → Form submissions, with the submitted values, uploaded files, sender IP and a preview of the sent e-mail. Submissions can be filtered and exported to CSV or JSON without any coding.

Hi Luis, sorry for the trouble. The form is submitted with AJAX, so the page is not reloaded: the success message appears in place of the form, and a redirect happens only when you set one in the form options. If the page does reload, the layout is missing the AJAX framework. Make sure it contains:

{% framework extras %}
{% scripts %}

If you need help, please open an issue on GitHub Issues.

Thank you, Allan! Calculating fields aren't built in yet. For now you can create a custom field type under Form Builder → Field types with a small script in its markup that computes the value from other inputs, for example into a read-only or hidden field, which then gets stored with the submission. If you'd like it as a built-in field type, please add it as a feature request on GitHub Issues.

Hi Patrick, sorry for the short reply back then. The error doesn't come from Form Builder: martin.forms is the namespace of another plugin, Magic Forms. It usually means a page, partial or mail template still references that plugin after it was removed or disabled. Remove the reference and clear the cache with php artisan cache:clear.

If Form Builder gives you any trouble, please report it on GitHub Issues.

Thank you, Richard! There's no built-in model binding, but events cover both directions. Fill fields from any model before rendering, and save the submission to your own model after validation:

Event::listen('formBuilder.overrideField', function ($field, $form) {
    if ($field->name === 'email' && $user = Auth::getUser()) {
        $field->default = $user->email;
    }
});

Event::listen('formBuilder.formSubmitted', function ($form) {
    Lead::create(post());
});

See the Events section of the documentation for details.

Thank you, Ran, for the kind words! Duplicating a form is available now: use the copy button in the Actions column of the forms list. Since version 5.2.0 the copy also keeps the RainLab Translate translations.

Hi Madars, thanks for the question! Not out of the box: the Country select field uses RainLab Location's form_select_country(), which renders a native <select>, and native selects can't show images. You can create a custom field type under Form Builder → Field types that wraps the select with a JavaScript select library supporting option templates (for example Tom Select) and adds the flags there. If you'd like it built in, please add a feature request on GitHub Issues.

Hi Dinesh, thanks for the review! Both are available as field types:

1. Install the RainLab Location plugin.
2. Add a Country select field and a State select field to your form.

The state list refreshes automatically when a country is chosen, and the mail and the submission log show the country and state names. Both field types are described in the plugin documentation.

Sorry for the unhelpful reply back then. The plugin has been updated many times since and is actively maintained for October CMS 4. If you still run into a problem, please describe it on GitHub Issues and I'll help you there.

Thank you, Paddy! Glad it saved you the day. That's exactly what the plugin is for.

Hi Kai, thank you, and sorry for the very late reply.

0. Please ask on GitHub Issues.
1. Yes. Every submission is already stored in the database under Form Builder → Form submissions, where you can view, filter and export it, but not edit it.
2. For editable rows, create a Tailor blueprint (October CMS 3 and 4) for your table. You get the backend list and edit form without writing a plugin. Then copy each submission into it with one event listener:

Event::listen('formBuilder.formSubmitted', function ($form) {
    if ($form->code === 'my-form') {
        $entry = \Tailor\Models\EntryRecord::inSection('Leads');
        $entry->fill(post());
        $entry->save();
    }
});

The form has no action field because it's submitted with AJAX to the component. Events are the way to hook into it.

Hi Sally, thank you for the detailed feedback, and sorry for the very late reply. Most of it is addressed now:

• The reCAPTCHA field renders its label.
• The documentation covers using form data in mail templates, and the mail itself is sent through October's Settings → Mail Configuration.
• Instead of a video, there's a live demo; the login details are in the plugin description.

The default field markup uses Bootstrap 5 classes. With another CSS framework, edit the markup under Form Builder → Field types. Thanks for pointing it out, I'm adding it to the documentation.

Hi, thanks for the honest review, and sorry for the trouble back then. The errors came from RainLab Translate itself and were worked around in 1.2.9. Today Form Builder works with RainLab Translate and October's multisite: form names, labels, options, messages and validation messages are translatable, and since 5.2.0 duplicating a form keeps its translations. Support for October's native translations is on the roadmap.

If anything still breaks, please report it on GitHub Issues.

Thank you, Gerald!

Thank you, Gerald, for the kind words! By the way, the plugin is fully translated into German.

Thank you, glad you like it!

Thank you, Vijay, for the kind words!

Thank you!

Thank you, Tyson, for the kind words and the recommendation!

Thank you, Nick! Labels can be styled per field now: set Label CSS classes in the field's HTML & CSS tab. For full control, the label markup of each field type is editable under Form Builder → Field types.

Thank you, Elian, for the kind words and the recommendation!

Thank you, Juan, for the kind words and the recommendation!

Thank you, MyeongCheol!

Thank you, glad to hear it!

Thank you, Marina, that means a lot! By the way, since version 5.2.0 the plugin is fully translated into Russian.

Thank you for the kind words!

Thank you, Andy, glad it serves you well!

Thank you so much for the kind words and for recommending my plugins!

Thank you, Gavin, for the kind words! A small tip: the form component is now registered as a RainLab Pages snippet itself, so clients can drop any form into a page and choose it there, without a separate partial for each form.

Hi Daniel, sorry for the reply back then. All three are covered now:

• Date, Time and Datetime are built-in field types, together with E-mail, Phone, URL, Numeric and Color Picker.
• Columns: give each field a wrapper class such as col-md-6, or lay the form out freely in the form's Custom Template tab.
• Wizard (multi-page) forms are on the roadmap.

If you need help, please ask on GitHub Issues.