Releases: verbb/formie
Releases · verbb/formie
3.1.21
Added
- Add
emailvariable to email notification templates, exposing the composed Craft mail message (including parsedsubject). - Add missing translations for the form builder.
- Add missing translations for the form builder.
Fixed
- Fix Date field normalization for single-value fields (like Year-only, etc).
- Fix entry element integration field mapping for legacy IDs and nested groups.
3.1.20
Added
- Add
PaymentSuccessRedirectEventto manage the redirect for some payment providers. - Add optional “Paste as Plain Text” setting for Multi-Line Text fields using the front-end rich text editor.
- Add support for
cleanPastefor Tiptap rich text fields. - Add
Dotdigital::EVENT_MODIFY_ADDRESS_BOOKSevent. - Add note to DotDigital Address Book regarding List.
- Add “Form” conditions for Form element source conditions.
Changed
- Improve client-side handling of conditional page logic.
Fixed
- Fix payment webhook redirects not allowing dynamic variables in the URL.
- Fix an error when redirecting payments via webhooks.
- Fix an issue for GoCardless and Mollie when their respective payment fields are hidden.
- Fix Craft
BaseRelationFieldcheck so entry integrations decode relation IDs from JSON strings. - Fix captchas and payments not working correctly in some cases, when combined, when additional client-side action was required.
- Fix Captcha.eu front-end refresh handler for success.
- Fix an issues with synced fields and shared content handling.
- Fix an issue with Captcha.eu integration.
- Fix Salesforce integration Date/Time values.
- Fix GraphQL mutations leaking schema details.
- Fix statuses not persisting correctly on first installation on new environments.
2.2.18
Fixed
- Fix an issue with Captcha.eu integration.
- Fix statuses not persisting correctly on first installation on new environments.
- Fix Captcha.eu lacking graphql variables.
3.1.19
Added
- Add support for non-public asset uploading with HubSpot forms.
- Add GraphQL variable support for CaptchaEu.
Fixed
- Fix an issue with page-level conditions not treating conditionally hidden fields correctly in some cases.
- Fix Table fields and their inner field required state for validation.
- Fix encoding of
<and>characters in field values.
3.1.18
Fixed
- Fix options-fields (particularly Checkboxes) settings their defaults when an empty value is submitted.
- Fix field normalizer for some removed properties.
- Fix an error for options-based fields not properly handling their value for dynamic Payment field amounts.
- Fix Repeater field conditions evaluations not working with the correct serialized field values.
- Fix visuals for single-option limited Phone fields.
- Fix Stripe
Submissions::EVENT_AFTER_SUBMISSIONtriggered on the wrong class. - Fix an error with Craft 5.8 and Forms/Submissions element fields.
2.2.17
Fixed
- Fix visuals for single-option limited Phone fields.
3.1.17
Added
- Add status support for Freeform 5 submission migration.
- Add “Block Free Email Providers” setting to Email fields.
- Add the
—update-titlecommand argument toresave/submissionscontroller command.
Changed
- Update Flatpickr UI to reflect Time Format settings (particularly for AM/PM).
- Remove debug customer for Paddle.
- Remove debug customer for Paddle.
Fixed
- Fix Repeater field conditions evaluations not working with the correct serialized field values.
- Fix an error with Stripe requests and invalid token handling.
- Fix lack of support for
scriptAttributeswith Table/Repeater<script>elements. - Fix an issue with
formie/gc/prune-data-retention-submissionsto finding all available submissions. - Fix an error when saving field layouts for complex fields that might contain closures.
- Fix ampersand encoding in field values.
- Fix Forms and Submissions element fields not allowing hyperlink to elements.
- Fix Forms and Submissions element fields allowing invalid view modes.
- Fix handling of plugin checks for fields that require plugins (Commerce).
- Fix an error when saving field layouts for complex fields that might contain closures.
- Fix Freeform 5 migration not honoring current submission titles.
- Fix an error when calling
Submission::getValues().
2.2.16
Changed
- Remove debug customer for Paddle.
Fixed
- Fix handling of plugin checks for fields that require plugins (Commerce).
3.1.16
Added
- Add support for Friendly Captcha v2 (opt-in).
Changed
- Update ElementSelect Model from DOM nodes and respect DOM order.
- Update Opayo API endpoints to align with latest API changes.
Fixed
- Fix Group and Repeater email templates not filtering out conditionally-hidden inner fields.
- Fix Repeater field conditions evalutations not working with the correct serialized field values.
- Fix Group field conditions evalutations not working with the correct serialized field values.
- Fix Date fields not populating their value correctly for conditions for some display types (inputs/dropdowns).
- Fix an error for client-side validation not showing inline errors.
- Fix showing “Public URL” as an Email Notification Value for File Upload fields when allowPublicVolumes was false.
- Fix an error when trying to use element select modals within field edit and other Vue-based modals.
- Fix an error during form plugin migrations where a backup could fail.
- Fix an issue with Summary fields not always generating a valid handle.
- Fix an issue with Section fields not always generating a valid handle.
- Fix “Advanced” and “Templates” tabs for Email Notifications not working correctly when setting per-form user permissions.
2.2.15
Changed
- Update Opayo API endpoints to align with latest API changes.