Releases: verbb/formie
Releases · verbb/formie
3.1.11
Added
- Add
CSRF_TOKENto unload exception for front-end forms. - Add
data-form-handleto<form>tag. - Add
beforeInitfor Phone field’sintl-tel-inputJS library.
Changed
- Bump
verbb/auth. - Remove
voku/anti-xssdependancy, and switch to HTMLPurifier. - Change user-related variables to always use the Submission’s “collected user” rather than the currently logged-in user.
Fixed
- Fix session-based page management for the front-end not respecting the
sessionKeyrender option. - Fix Phone field front-end not respecting countries set via
Countries::EVENT_MODIFY_PHONE_COUNTRIES. - Fix Table field not acting correctly when set to “required”.
- Fix Web Request integrations not setting the correct URL when migrated from previous Formie Webhook integration.
- Fix session storage checks for web-driven Queue jobs.
2.2.10
Added
- Add
data-form-handleto<form>tag.
Changed
- Change user-related variables to always use the Submission’s “collected user” rather than the currently logged-in user.
Fixed
- Fix Web Request integrations not setting the correct URL when migrated from previous Formie Webhook integration.
3.1.10
Fixed
- Fix a Twig error introduced in Craft 5.9+ for some fields.
- Fix an error for Freshdesk tickets.
3.1.9
Added
- Add
allowPublicVolumesplugin setting to allow only showing private (non-public URL) asset volumes for File Upload fields. - Add extra log output when failing garbage collection jobs for submissions.
Changed
- Improve client-side validation when using “live” validation mode (as the user types).
- Improve Date field sub-field cleanup when toggling between display types.
- Improve Name field sub-field cleanup when toggling between multi-name and single-name displays.
- When pruning spam submissions in garbage collection, submissions are now hard-deleted.
Fixed
- Fix form usage site/element table order.
- Fix client-side validation using click events to evaluate.
- Fix field handles not generating correctly when deleting and adding fields at the same time with the same handle.
- Fix Date fields with default values not showing correctly in the form builder for various displayTypes.
- Fix Formie 2 migation for Date fields for display type Dropdowns and Inputs not respecting their previously enabled sub-fields for date/time.
- Fix Date field Dropdowns and Inputs display types not showing enabled sub-fields correctly in the form builder.
- Fix Formie 2 migration for Date fields not working correctly for Inputs or Dropdowns.
- Fix an error for integrations used across multiple forms, where different forms enabled different data objects, and mapping lost.
- Fix Date/Time Dropdown Year validation.
- Fix Date with Text Inputs submission after 3.1.7.
- Fix field conditions not working correctly for content encrypted fields.
- Fix incorrect handling of integration connected state.
- Fix pruning spam submissions not working correctly.
- Fix lack of success checks for garbage collection console commands.
3.1.8
Fixed
- Fix memory limits for garbage collection tasks.
- Fix lack of console output for garbage collection tasks.
- Fix an error when using Date/Time fields and populating or setting default values for calendar displays.
- Fix an error handling email notification “from” values when also setting a “from name”.
- Fix Make the url encoding keep the ampersand unencoded.
2.2.9
Fixed
- Fix an error handling email notification “from” values when also setting a “from name”.
- Fix Make the url encoding keep the ampersand unencoded.
3.1.7
Added
- Add
FieldValueInterfacefor model classes that represent the value of a field. - Add
enableJsEventsandjsGtmEventOptionstoPageSettingsInterfacefor GraphQL. - Add support for Formie Address Country to Craft Country field for Element integrations.
Changed
- Update form import/export to be compatible with
tempAssetUploadFs. - Change submission behaviour when editing in the control panel when form settings like scheduling is enabled.
- Element integrations now handle array-like values for relation fields.
Fixed
- Fix Date/Time fields for Dropdowns or Inputs not having their values treated consistently.
- Fix compatibility with Craft 5.9+.
- Fix element fields not showing their correct values in the submissions index in the control panel.
- Fix an error with File Upload fields with Feed Me.
- Fix unload warning for Snaptcha.
- Fix an error where “From” email notification values weren’t always properly parsed.
- Fix conditional logic handling for Repeater fields.
- Fix an error with Date fields in Repeater fields failing Year restriction validation.
- Fix number input fields in the form builder for Firefox.
- Fix an error where “From” email notification values weren’t always properly parsed.
- Fix Opayo and Moneris iframe event handling registration.
- Fix an error for Opayo billing name mapping.
- Fix overflow for IP Address values (particularly v6) when editing a submission in the control panel.
- Fix Pardot integration JSON/XML responses.
- Fix Pardot CRM base API URL.
- Fix Zoho CRM base API URL.
- Fix Pardot API scope.
- Fix cache-handling for integration connections.
- Fix deprecation error for
log()calls. - Fix an error using OopSpam.
2.2.8
Changed
- Element integrations now handle array-like values for relation fields.
Fixed
- Fix cache-handling for integration connections.
3.1.6
Added
- Add
onFormieValidateErrorJS event for client-side error handling. - Add
isNewSubmissionargument to GraphQL mutation for submissions. - Add debug logging for reCAPTCHA responses.
Changed
- Webhook-based payment integrations (Mollie, GoCardless) now properly fire integrations and notifications.
- Improve front-end JS event management, to better deal with accidental multiple initialization of Formie’s JS in some setups.
- Question captcha protects against validation when no questions are set.
- Captchas for GraphQL mutations now don’t require a mandatory variables parameter to be named the same as their input type.
Fixed
- Fix handling of integration settings when connecting.
- Fix Date (Time-only) fields and validation handling.
- Fix an issue with event-binding for front-end JS.
- Fix an import form issue when updating an existing form, where notifications weren’t being treated correctly.
- Fix Payment fields displaying in Summary field content by default.
- Fix Date/Time fields not using min/max values for native date input for non-Flatpickr.
- Fix synced fields overriding the required attribute.
- Fix Name Prefix field not showing its value correctly in email notifications.
- Fix Name Prefix field values not getting properly translated.
- Fix an error for integrations used across multiple forms, where different forms enabled different data objects, and mapping lost.
- Fix email notifications containing .env variables as conditions not working correctly.
- Fix
isNewSubmissionflag for GraphQL mutations for submissions, causing multiple notifications to be sent when conditions exist and were met. - Fix mapping issues for Pipedrive Leads.
- Fix an error with Ortto and fetching lists.
- Fix HubSpot CRM integration handling of multi File Upload field values.
- Fix HubSpot field mapping for form company fields.
- Fix an error with handling Date field values (for date-picker fields) when in the control panel.
- Fix Formie 2 email notification migration for fields used in conditions.
- Fix an issue with Date fields, where the
availableDaysOfWeekmay not be typed correctly in some instances. - Fix an issue with ReCAPTCHA Enterprise validation.
- Fix a 3DS processing issue for Moneris and Opayo in some setups.
- Fix an error when programatically changing the available countries to a Countries field.
- Fix Opayo, Stripe and Paddle Payment integrations incorrectly setting the Billing Address value for payments.
- Fix some missing properties for Date fields when querying via GQL.
- Fix some complex fields not having their error messages set when editing a submission in the control panel.
- Fix fetching an email signature controller action using CSRF verification when it doesn’t need to.
2.2.7
Added
- Add debug logging for reCAPTCHA responses.
Changed
- Webhook-based payment integrations (Mollie, GoCardless) now properly fire integrations and notifications.
- Question captcha protects against validation when no questions are set.
- Captchas for GraphQL mutations now don’t require a mandatory variables parameter to be named the same as their input type.
Fixed
- Fix Payment fields displaying in Summary field content by default.
- Fix Date/Time fields not using min/max values for native date input for non-Flatpickr.
- Fix an issue with Date fields, where the
availableDaysOfWeekmay not be typed correctly in some instances. - Fix an issue with ReCAPTCHA Enterprise validation.
- Fix fetching an email signature controller action using CSRF verification when it doesn’t need to.