Added
- Added
summaryTokensto client-rendered form submission results, including thesubmitFormieClientFormGraphQL mutation, so Summary fields can show the answers saved so far. (#3146) - Added Link and Control Panel Link to the notification content variable picker for Entries, Categories, Tags, Users, Products, Variants and File Upload fields. They’re written as the picked element’s label linked to its page. (#3142)
- Added element details to the variable picker for element fields: ID for all of them, Slug, Section, Entry Type, Post Date, Status and Author for Entries, Slug and Group for Categories, Group for Tags, and Name and Username for Users. See Element Field Tokens.
Changed
- Client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components now mark required fields withdata-formie-field-requiredon the field andaria-requiredon its control, so themes can style them and screen readers announce them. (#3139) - Client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components now link each field’s label to its control, so clicking the label focuses it, and describe the control with the field’s instructions. Radio, Checkboxes and Agree fields are grouped and named by the field label, as in server-rendered forms. (#3140) - A form’s Usage tab and Usage Count column now load the elements that select the form, and their owners, in batches. Forms selected in Matrix entries or Content Blocks no longer need several database queries for each usage. One test form with 372 usages went from 1,720 queries to 55. (#3150)
- The Save Spam Submissions setting now explains that requests rejected by submission guards, such as a filled-in honeypot, are never saved and are written to the Formie log instead. In Formie 3, honeypot catches were saved as spam submissions. (#3151)
Fixed
- Fixed a moderate-severity information disclosure vulnerability.
- Fixed forms with two Stripe Payment fields switched by conditions charging the card but never finishing the submission when the second field was the one shown. The hidden field confirmed the payment and kept the payment ID in its own input, so the submission was left incomplete and the form kept loading. (#3153)
- Fixed “This Element has already been destroyed.” errors in the browser console after a Stripe payment on forms that hide after submitting. (#3153)
- Fixed Payment fields inside Group and Repeater fields still showing their label with an empty value in submission summaries.
- Fixed payment webhooks never arriving on sites with Craft’s
devModeon, including publicly reachable staging sites. Stripe, GoCardless and Mollie webhook URLs were sent through Verbb’s development proxy, which can only redirect, so every webhook failed. If you copied a webhook URL starting withhttps://proxy.verbb.iointo your Stripe or GoCardless dashboard, replace it with the one now shown in the integration’s settings. Mollie payments on local sites that Mollie can’t reach, such aslocalhostor a.testdomain, are now created without a webhook URL and checked with Mollie when the visitor returns. - Fixed forms not working on pages that use the deprecated
craft.formie.registerAssets()orcraft.formie.registerFormAssets(). These pages got no Formie JavaScript at all, so forms had no validation, Ajax submissions or captchas. The helpers now add the form’s CSS and JavaScript to the page again, as in Formie 3. - Fixed saving an integration clearing the fields it had fetched from the provider, such as Salesforce, which made its mappings show No fields available. in the form builder and sent submissions without their mapped values. Integrations now keep their fields unless a connection setting changes. Click Refresh on each mapping of an integration that’s already affected to show its mappings again.
- Fixed CRM, email marketing, help desk, Monday, ClickUp and Recruitee integrations sending submissions without any of their mapped values when the provider’s fields hadn’t been fetched, such as after connecting a different account. Mapped values are now sent as they were in Formie 3 until Refresh fetches the fields.
- Fixed integration mappings showing as blank in the form builder on multi-site installs upgraded from Formie 3, for forms that weren’t on the primary site. The upgrade skipped these forms, so their mappings, notification variables and other field references kept their Formie 3 field handles. Updating converts them.
- Fixed forms using Friendly Captcha submitting before the challenge was solved, so the submission failed verification and was treated as spam. The form now starts the challenge on submit and waits for its solution. (#3151)
- Fixed forms starting twice when a page loads Formie’s JavaScript from two different URLs, such as cached markup that still points at the files from an earlier Formie version. reCAPTCHA v3 then rendered two widgets, so submissions took around 30 seconds and were saved as spam with “Client-side token missing.” Formie now starts once per page. A page that still loads files from a version before this fix also needs its cache cleared. (#3152)
- Fixed Dropdown option labels not being translatable per site in the form builder. Changing an option label while editing another site changed it on every site instead. (#3145)
- Fixed option labels not being translatable per site for options with an empty value, such as a Dropdown’s “Choose a language” prompt. Changing the label while editing another site wasn’t saved, and front-end forms kept showing the source site’s label.
- Fixed a form’s Usage tab and Usage Count column leaving out the element that owns a nested element of another type, such as the entry that owns a Content Block selecting the form. (#3149)
- Fixed Address fields using Google Places keeping the previous street in Address 1 when a suggestion without a street, such as a postcode, was picked after a full address.
- Fixed Recipients fields that aren’t required showing “Select a valid recipient.” and stopping the submission when left unanswered. This affected the Radio display type and Dropdowns with an empty first option.
- Fixed Calculations fields in Repeater rows always showing 0 when their formula used another field from the same Repeater. Each row now uses its own row’s field.
- Fixed File Upload fields using the Upload Manager showing a smaller size than Max File Size or Min File Size in their file size errors, such as 4.8 MB for a 5 MB limit. (#3143)
- Fixed Address Country, Date dropdown parts, Group, Table, Recipients and Section fields, and Entries, Categories and other element fields, showing “Unsupported field type” in client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components. A form with a Recipients field couldn’t be submitted. - Fixed answers to Survey fields with a Likert scale with multiple rows being left out of integration payloads and other submission data.
- Fixed File Upload fields with the Upload Manager (Advanced) display type showing a plain file input in client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components. They now show the Upload Manager, which uploads each file as soon as it’s chosen, including in Repeater rows and Groups. (#3146) - Fixed Dropdown, Recipients and element fields with Use Searchable Dropdown showing a plain select in client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components. They now show the searchable dropdown, including for multiple choices. (#3146) - Fixed Date fields with the Calendar (Advanced) display type showing separate date and time inputs in client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components. They now show the date picker, including for date ranges, and save the same answer as server-rendered forms. (#3146) - Fixed Multi-line Text fields with Use Rich Text Field showing a plain textarea in client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components. They now show the rich text editor and save its HTML, as in server-rendered forms. (#3146) - Fixed Table checkbox cells being saved as
trueorfalsefrom client-rendered forms and the API, where form posts save1or nothing. Checkbox cells are now stored the same way whatever sent them, including in existing submissions when they’re read. (#3146) - Fixed Checkboxes fields, and Survey and Quiz fields shown as checkboxes, not showing their “Select all” checkbox in client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components. (#3146) - Fixed Summary fields showing “Unsupported field type” in client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components. They now show the answers saved so far once a page is submitted, as in server-rendered forms, including when the form is on another site. (#3146) - Fixed Survey fields with the Likert, Rank, Rating, Dropdown, Single-line Text or Multi-line Text display types showing “Unsupported field type” in client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components. Rank items can be moved with Move up and Move down buttons as well as dragged. (#3146) - Fixed Hidden fields that take their value from a cookie, query parameter, the current URL or the referring URL getting nothing or the wrong value in client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components. They now read it from the visitor’s page, as server-rendered forms do. (#3146) - Fixed Password fields’ minimum length, uppercase, lowercase and special character requirements only being checked by the server in client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components. (#3146) - Fixed Address fields with an auto-complete provider stopping client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components from being submitted, with “A required form feature could not start”. Google Places, PlaceKit, Loqate and AddressFinder now fill the address as in server-rendered forms, and Use my location shows when it’s turned on. (#3146) - Fixed Payment fields showing “Unsupported field type” in client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components, so a form with a Payment field couldn’t be submitted. They now show the provider’s own payment form, and payments that need confirmation, such as 3D Secure, or a redirect to the provider’s checkout continue as in server-rendered forms. (#3146) - Fixed Phone fields with Country Enabled showing a plain input with no country picker in client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components, so the visitor’s country was never sent. Typing a number in any Phone field also replaced the answer with the number alone, and a required Phone field with a default country passed the form’s own validation while empty. (#3146) - Fixed Calculations fields never showing their answer, and accepting typing, in client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components. This includes Calculations fields in Groups and Repeater rows, where a field from the same Repeater is read from the calculation’s own row. - Fixed client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components not showing the page title of forms that turn on Display Current Page Title, or the progress bar of multi-page forms that turn on Display Page Progress. - Fixed Dropdown fields showing their first option while sending no answer, and multi-select Dropdown fields not showing their default options as selected, in client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components. - Fixed Radio options not working with arrow keys in some browsers in client-rendered forms, and choosing a Radio option in one Repeater row clearing the same field in another row in the Formie web components.
- Fixed client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components leaving focus nowhere after a page change or a completed submission, and not announcing form errors or completion messages to screen readers. - Fixed Name, Address, Date and Group fields not naming their parts as a group, labels in the Hidden position showing, and inputs missing the autocomplete hints that server-rendered forms use, in client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components. - Fixed Repeater Remove buttons not saying which row they remove, and Repeater, Table and Signature buttons showing in English, in client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components. Repeater errors also showed twice with@verbb/formie-vueand@verbb/formie-react. - Fixed Repeater row fields with Visibility set to Hidden showing in client-rendered forms built with
@verbb/formie-vue. - Fixed custom React field components that use hooks causing React errors when a condition showed or hid their field.
- Fixed the Signature field in the Formie web components causing an unhandled error each time it loaded.
- Fixed the German and Italian translations of Move down, and the Italian translation of Move up, which read as scrolling instead of moving an item.
- Fixed the Spanish, German, French, Portuguese and Italian translations of Clear signature, which read as “legible signature”.
- Fixed around 200 messages in the German, Spanish, French, Italian and Portuguese translations showing placeholders such as
{Datum}, or the whole message pattern, instead of their values. These include character limits on text fields, minimum and maximum option errors, and subscription intervals. (#3144) - Fixed Dropdown fields rendering as a multi-select list, and File Upload fields accepting several files when they allow only one, in client-rendered forms built with the Formie web components.
- Fixed integrations failing with “Malformed UTF-8 characters” when an
EVENT_MODIFY_FIELD_MAPPING_VALUEShandler set a file attachment’s contents to binary data, such as a converted image. (#3138) - Fixed the Google Sheets integration being unable to load its sheets or add rows, and its Sheet setting missing a refresh button. (#3136)
- Fixed the Entries integration ignoring Default Entry Author and making user 1 the author of every entry it created. (#3131)
- Fixed Default Entry Author and the other element integrations’ default author showing no user in the form builder on forms upgraded from Formie 3. Upgraded sites are repaired when migrations run. (#3131)
- Fixed searchable dropdowns showing “No results found” and the Remove and clear button titles in English instead of the site’s language. (#3135)
- Fixed conditions on the Title or Public URL of an Entries, Categories or other element field never matching on the front end, as they compared the selected element’s ID. (#3133)
- Fixed the Settings item missing from a form’s Integrations tab when only one integration was enabled, so its order, notification timing and Apply recommended setup couldn’t be reached. (#3132)
- Fixed users and untitled entries chosen in the form builder, such as the Default Entry Author, showing as “Element 10” instead of their name after the form was saved. (#3131)
- Fixed Custom missing from the formats of the Date Format variable transform, which left no way to use your own date format, such as
d.m.Y. - Fixed variables using the Date Format transform showing a “Number Format” badge in the form builder.
- Fixed Link to an entry in the form builder’s rich text settings, such as an Agree field’s Description, never adding the link. The link dialog opened behind the field’s settings after choosing the entry. (#3141)
- Fixed notification content and messages adding an empty paragraph before All Fields, All Non Empty Fields, All Visible Fields or a whole Table, Repeater or Payment field when it was on its own line. (#3142)
- Fixed All Non Empty Fields leaving out unticked Agree fields. They’re listed with their Unchecked Value again, as in Formie 3. (#3142)
- Fixed opening a submission in the control panel creating its File Upload folder when the field’s subpath uses submission values, such as
{submission:id}, which left an empty folder for every submission opened. (#3134) - Fixed the Submissions index Export… dialog combining each Name and Address field into one column. Each part now has its own column, as in Formie 3, and the combined column can still be ticked. (#3055)
- Fixed client-rendered forms built with
@verbb/formie-reactmoving focus to the error message on every keystroke after a submit that failed validation, so only the first character typed was kept. - Fixed Single-line Text, Multi-line Text and Survey text fields with Limit Value not checking their limits or showing the limit counter in client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components. They now count down to the limit as server-rendered forms do, and don’t submit while an answer is outside its limits. (#3146) - Fixed Address fields with Input Mode set to Dropdown when available showing a plain text input for State / Province in client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components. It now lists the chosen country’s subdivisions, takes the name the country uses for them, such as Prefecture, and hides for countries that don’t use them, as in server-rendered forms. (#3146) - Fixed Custom fields wrapping a Craft Link field, or a Maps or Google Maps field, showing a single text input in client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components. They now show the link type, label and advanced options, or the map and its search, and save the same answer as server-rendered forms. (#3146) - Fixed client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components always showing a field’s label above its control, then its instructions and errors. They now follow the field’s Label Position, Instructions Position and Error Message Position, as in server-rendered forms. (#3146) - Fixed the Question captcha not showing its question in client-rendered forms built with
@verbb/formie-vue,@verbb/formie-reactor the Formie web components, so every submission failed the captcha. (#3146)