Releases: verbb/formie
Releases · verbb/formie
3.0.24
3.0.23
Added
- Add extra logging to Opayo payment failures.
- Add the ability to assign a Campaign to a Contact/Lead/Account in Salesforce.
- Add support for filtering submissions by fields in the control panel.
- Add the ability for HTML fields to reference render options via Twig in their content.
- Add the ability to provide submission query arguments for fields, for GraphQL.
- Add
Field::EVENT_MODIFY_VALUE_FOR_VARIABLE
. - Add the ability to set the permissions of newly-created forms for users that have limited form access.
Change
- Improve performance of submission editing screen in the control panel.
- Improve performance of submissions element index in the control panel.
- Improve field layout error output for nested fields and failed validation, which now references the page handle, field handle and any parent field handle.
- Update deprecated
log()
function. - Move
Field::getValueForVariable
toField::defineValueForVariable
.
Fixed
- Fix
submissionEndpoint
GraphQL property. - Fix an error for Phone fields, when initializing the form’s JS multiple times.
- Fix payment field race condition when initializing form JS multiple times with conditions.
- Fix an error with Opayo and billing email.
- Fix an XSS vulnerability for importing forms with manipulated field content.
- Fix an XSS vulnerability for email notification content.
- Fix support for Craft 5.7+.
- Fix submission titles displaying incorrectly when referencing some fields in their content.
- Fix Agree field not rendering its empty value correctly in email notifications.
- Fix email notifications not rendering empty valued fields correctly.
- Fix Pardot integration not working correctly. (thanks @mirego).
- Fix sub-field fields not having their label correctly set in some instances when upgrading to Formie 3.
- Fix an error with Summary and Section fields for Formie 3 upgrades.
- Fix large field settings throwing an error (particularly for Formie 3 upgrades).
2.1.44
Added
- Add extra logging to Opayo payment failures.
- Add the ability to assign a Campaign to a Contact/Lead/Account in Salesforce.
Fixed
- Fix
submissionEndpoint
GraphQL property. - Fix an error for Phone fields, when initializing the form’s JS multiple times.
- Fix payment field race condition when initializing form JS multiple times with conditions.
- Fix an error with Opayo and billing email.
- Fix an XSS vulnerability for importing forms with manipulated field content.
- Fix an XSS vulnerability for email notification content.
3.0.22
Added
- Add
Submission Date
to some field mapping controls. - Add support for Recipients field to set the “Email Notification Value”.
- Add back
Field::EVENT_MODIFY_VALUE_FOR_EMAIL
events to modify the value used in Email Notifications. - Add
SubmissionEvent::forceRedirect
option for events to force a redirect on form submission. - Add
Form::setRedirectEntry()
. - Add the ability to pass arguments to
templateJs
for GraphQL queries to control JS initialization.
Changed
- Improve performance of form usage for large sites and content structures.
- Improve Submission export performance, by removing eager-loading non Formie fields.
- Update
Field::defineValueForEmail
to return the raw value for the field, rather than the string-representation of the value. - Updated Feed Me integration for submissions to list forms in alphabetical order.
- Update GraphQL resolvers to use
ElementCollection
correctly.
Fixed
- Fix some errors with Submissions widget for invalid dates and
weekStartDay
user settings. - Fix an error when importing a form, made from an export from the Forms element index.
- Fix HubSpot GDPR processing when not enabled.
- Fix an issue with Iterable integration field mapping.
- Fix some fields not having their default values set correctly.
- Fix an error when importing a Formie 2.x export.
- Fix an issue where the row’s empty state wasn’t updated for nested or sub-fields using conditions.
- Fix an error when trying to query Form Template fields for a form with GraphQL.
- Fix Nested Fields not having their summary field values reporting correctly (value as string, json, exports, summary).
- Fix Stripe dynamic amount not processing currency values.
- Fix
providerSettings
when querying Payment fields in GraphQL. - Fix an error with Payment fields when viewing a submission in the control panel in some instances.
- Fix a race condition for Repeater fields when set to use a minimum number of instances.
- Fix Feed Me being able to map to cosmetic fields.
- Fix an error for Feed Me when mapping to element fields.
- Fix a display error when only “Fields” tab is available for editing, when editing a form.
- Fix an issue where a form’s UID could be out of sync.
- Fix redirect override when setting via the
EVENT_AFTER_SUBMISSION_REQUEST
event. - Fix an error where fields and rows were being incorrectly filtered when rendering a form multiple times.
- Fix when new Forms are created from a Stencil, their enabled captchas not being respected.
2.1.43
Added
- Add
Submission Date
to some field mapping controls.
Fixed
- Fix some errors with Submissions widget for invalid dates and
weekStartDay
user settings. - Fix an error when importing a form, made from an export from the Forms element index.
- Fix HubSpot GDPR processing when not enabled.
- Fix an issue with Iterable integration field mapping.
- Fix some fields not having their default values set correctly.
3.0.21
Added
- Add “Message Type” to Iterable CRM integration.
- Add the ability for IntegrationField’s to contain static
data
in their definitions. - Add support for Table field to use
id
orname
values when defining a row schema. - Add “Attach File Uploads” for all data objects for Salesforce integration.
Changed
- Improve Hubspot GDPR handling for marketing and processing options.
- Update Monday integration instructions.
Fixed
- Fix Agree field not allowing
null
value as an empty state indicator. - Fix Agree field markup to match correct accessibility guidelines.
- Fix Hubspot GDPR handling.
- Fix Monday integration connection requests.
- Fix an error when applying Formie-related project config when uninstalled.
- Fix Phone number fields flag icons in the form builder.
- Fix form usage throwing errors in some instances.
- Fix an error determining the default status for a submission, if none are set.
- Fix an error with Email Notifications when no valid fields could be found to be included in the email content.
- Fix Form Template setting not persisting for Stencils.
- Fix an error for captchas not rendering if the captcha placeholder was visually obscured.
- Fix Address and Multi-Name fields not working correctly when populating their field content.
- Fix Calculations field variables not being set correctly, when referencing other fields.
- Fix handling for some integrations where session data isn’t being persisted when connecting via OAuth.
- Fix server-side error messages for Repeater fields.
- Fix an error for File Upload fields with GraphQL, when min/max size limits were set.
- Fix a display issue for forms with multiple payment fields with the same integration.
- Fix payment summary display when editing a submission for Craft 5.6+.
- Fix multiple Payment fields not validating correctly when re-initializing the fields’ JS.
- Fix Phone Number server-side validation error.
- Fix an error with Stripe payments for subscriptions when including a payment receipt.
2.1.42
Added
- Add “Message Type” to Iterable CRM integration.
- Add the ability for IntegrationField’s to contain static
data
in their definitions. - Add support for Table field to use
id
orname
values when defining a row schema.
Changed
- Improve Hubspot GDPR handling for marketing and processing options.
- Update Monday integration instructions.
Fixed
- Fix Agree field not allowing
null
value as an empty state indicator. - Fix Agree field markup to match correct accessibility guidelines.
- Fix Hubspot GDPR handling.
- Fix Monday integration connection requests.
- Fix an error when applying Formie-related project config when uninstalled.
- Fix Phone number fields flag icons in the form builder.
3.0.20
Added
- Add
Submission::getFormHandle()
.
Changed
- Refactor queue jobs to provide better feedback on errors and logging data.
- Improve queue job feedback on error to include the payload being sent.
Fixed
- Fix an error with Group and Repeater fields with required File Upload fields on multi-page Ajax forms.
- Fix Group and Repeater fields not respecting “Include in Email Notifications” setting and conditionally hidden fields in email notifications.
- Remove incorrect
Campaign = Kampagne
German translation for the Campaign plugin. - Fix Single-Line text fields in the control panel not showing limit details correctly.
- Fix Multi-Line text fields in the control panel not showing limit details correctly.
- Fix new email notifications not having the conditions logic set correctly.
- Fix email notification queue job causing an infinite loop in some scenarios, and provide better logging feedback.
- Fix an error in Craft 5.6+ where fields’
queryCondition()
function wasn’t being called. - Fix some sidebar elements not displaying correctly when editing submissions in the control panel on Craft 5.6+.
2.1.41
Fixed
- Fix an error with Group and Repeater fields with required File Upload fields on multi-page Ajax forms.
- Fix Group and Repeater fields not respecting “Include in Email Notifications” setting and conditionally hidden fields in email notifications.
- Remove incorrect
Campaign = Kampagne
German translation for the Campaign plugin.
3.0.19
Changed
- The
intl-tel-input
for Phone number fields no longer lazy-loads it’s utilities script. - Update
intl-tel-input
for the latest number validation handling. - Fields in email notification content, when referenced via their variable tag now no longer show their “no response” placeholder text. These still exist for grouped content like “All Fields”.
Fixed
- Fix incorrectly bundled
intl-tel-input
version. - Fix some string content not being escaped properly.
- Fix Freeform 5 migration for success behaviour.
- Fix default value for Date field not being set correctly.
- Fix File Upload handling for some database engines (MariaDB).
- Fix an error with Entry element integrations when updating values.
- Fix email notifications table when columns contained long variable tags.
- Fix incorrect logic when calling
Notifications::getFormNotificationByHandle()
.