github verbb/formie 4.0.10

one hour ago

Added

  • Added a Camel Case text transform for references.

Fixed

  • Fixed a cross-site scripting vulnerability.
  • Fixed Table and Repeater fields being left out of notification content, and Payment fields showing raw provider data, when the whole field was referenced as it was in Formie 3.
  • Fixed custom integrations using verbb\formie\base\Webhook, ModifyWebhookPayloadEvent, EVENT_MODIFY_WEBHOOK_PAYLOAD, getWebhookUrl() or $event->webhooks failing after upgrading from Formie 3. These names still work, and the upgrade guide lists their replacements.
  • Fixed condition rules that read a field placed later in the form, such as those upgraded from Formie 3, showing no field in the form builder.
  • Fixed Agree fields missing from the field list when setting up conditions. Rules on an Agree field now offer Checked and Unchecked, as they did in Formie 3. (#3127)
  • Fixed forms silently sending nothing to integration providers Formie 4 no longer includes, such as HubSpot (Legacy). Each submission now logs a warning naming the provider. See the upgrade guide.
  • Fixed stencils left with fields of unknown types after upgrading from Formie 2, which made forms created from them unusable.
  • Fixed Recipients fields shown as checkboxes leaving their selections out of {allFields} in email notifications.
  • Fixed fields never showing when a condition compares a Number field with an empty value, such as “is not empty text”, or when “is” or “is not” compares an unanswered Number field.
  • Fixed answers being lost from fields shown by a condition on a Date field’s Year, Month or Day dropdown. The condition matched in the browser, but the server couldn’t read the value, so it cleared the answer when the form was submitted.
  • Fixed Form Templates upgraded from Formie 3 loading CSS or JavaScript that was turned off there, when only its nested theme setting was left on. Upgraded sites are repaired when migrations run, unless the template has been saved since.
  • Fixed Payment fields showing raw provider IDs in submission summaries.
  • Fixed the format reference transform, and Submission Date mapped to an integration date field, changing the time by the site’s UTC offset. HubSpot received the Submission Date up to 20 hours out for a site in Melbourne.
  • Fixed submission titles missing values when Submission Title Format used the submission’s ID or date, or fields on later pages.
  • Fixed the progress bar’s percentage showing on upgraded forms with Progress Value Position set to Hidden, and sitting on its own line when set to the left or right of the bar.
  • Fixed fields without a label, such as headings, being squeezed into the label column when the label position is Left of Input or Right of Input.
  • Fixed the form’s Default Label Position being ignored when set to Left of Input or Right of Input, showing labels above or below the field instead.
  • Fixed failed notification alert emails leaving out why the notification failed.
  • Fixed notifications with Attach PDF Template enabled failing to send when no PDF template was selected, instead of attaching the default PDF.
  • Fixed notifications failing to send when a subject or From name contained brace text that can’t be a variable, such as {(Enquiry)} or {foo bar}. It now stays as written, including in the email body, and recipient settings still reject it.
  • Fixed a notification that failed before sending, such as on an invalid PDF filename or sender, being reported as an unknown delivery that blocked resending, with no entry in Sent Notifications.
  • Fixed element integrations blanking existing content from empty answers when Overwrite Content is off.
  • Fixed the User element integration sending activation emails while Send Activation Email showed as off. The form builder showed it, and Update Search Index on User and Entry integrations, as off until saved, while submissions used them as on. They now show their actual setting. (#3129)
  • Fixed integrations failing every send with “Reference resolution failed: missingField” after a mapped field was deleted from the form. The mapping showed Don’t Include but still pointed at the deleted field. Saving the form now clears it, which also repairs forms already affected. (#3128)
  • Fixed page tabs on page-reload forms showing visitors a “Post request required” error page. Tabs now change page the same way on both submit methods, and an earlier tab error clears once a page change succeeds.
  • Fixed editing a completed multi-page submission on the front end saving it from the first page, so the later pages couldn’t be reached. Its pages now change in the browser, and the last page saves the answers from every page once. (#3126)
  • Fixed Scroll To Top not returning to the top of the form when moving to another page on AJAX forms, leaving visitors at the bottom of the next page.
  • Fixed visitors seeing an error page when a form with an unanswered Table date or time column failed validation.
  • Fixed forms with a Tags field being unable to submit with “Select only valid options” when the field was left blank.
  • Fixed the “Reassign submissions” modal throwing an error when deleting a user on Craft 5.10 to 5.11.1.
  • Fixed saving the field palette throwing an error instead of reporting that it couldn’t be saved, such as when two groups share a handle.
  • Fixed craft.formie.getLabelPosition() always returning Above Input when asked for a sub-field label position.
  • Fixed deleting a payment integration with active subscriptions throwing an error instead of explaining why it can’t be deleted.
  • Fixed email notifications failing with “Reference resolution failed: missingField” after upgrading from Formie 3 when a setting such as the subject included a whole field with sub-fields, such as Name or Address. Upgraded sites are repaired when migrations run. (#3123)
  • Fixed conditions saved in older formats never matching after upgrading from Formie 3 or 2, which left fields hidden, notifications unsent and the builder showing no field. This covers Group paths such as {field:group.rows.new1.fields.child}, bare tokens such as {handle} and same-row Repeater sources such as {field:repeater.__ROW__.child}, on fields, pages, form rules, notifications and conditional recipients. Some of these rules never matched on Formie 3 either, so they now take effect for the first time. Upgraded sites are repaired when migrations run. (#3087)
  • Fixed File Upload subpaths and filenames, submission title formats, success messages, redirect URLs, Hidden field defaults, payment amounts, currencies, descriptions and billing details, integration messages and Webhook URLs from Formie 3 or 2 failing or losing values when they named a field as {handle}, {handle.part}, {field.handle}, {group[child]} or {field:handle}. Simple Twig filters in File Upload paths, such as {postDate|date("Ymd")}, {formName|camel} and {owner.id}, are converted too. Upgraded sites are repaired when migrations run.
  • Fixed forms imported from a Formie 3 or 2 export, or created from a stencil, keeping old field tokens in their settings and conditions, so they failed, lost values or kept fields hidden in the same way. Stencils saved before upgrading, including those in project config, are converted when migrations run.
  • Fixed a Password field’s stored hash being written into notifications and other settings that reference the field.
  • Fixed email notifications from Formie 3 leaving out a Recipients field’s selected label or email address when they used {handle.label} or {handle.value}. Upgraded sites are repaired when migrations run.
  • Fixed exporting a report to Excel failing when an answer was longer than an Excel cell can hold (32,767 characters), such as a Signature drawn with many strokes. Excel exports now cut those answers to fit, and other formats keep them whole. (#3125)
  • Fixed upgrading from Formie 4.0.0-beta.10 to 4.0.0-beta.16 failing with “Setting unknown property: verbb\formie\models\FormSettings::integrationPolicies” when migrations ran.
  • Fixed report date bounds using UTC instead of the site’s time zone. On sites ahead of UTC, Today’s Date/Time could fall on the previous day, and report tables and exports left out recent submissions that the summary counted. Specific Date/Time bounds moved by the site’s UTC offset each time a report was saved, so check any set before this fix. Report charts and scheduled report start and end dates now follow the site’s days too.

Don't miss a new formie release

NewReleases is sending notifications on new releases.