Skip to content

Releases: verbb/formie

1.6.43

31 May 11:21
Compare
Choose a tag to compare

Fixed

  • Fix an error when submitting a form and manipulating the goingBack param.

3.0.0-beta.13

29 May 04:47
Compare
Choose a tag to compare
3.0.0-beta.13 Pre-release
Pre-release

Added

  • Added sizeLimit, sizeMinLimit and limitFiles to File Upload GraphQL queries.

Changed

  • Update Payment fields to provide a more client-friendly error message when a payment fails.
  • Ensure that sessions exists when calling formie/forms/refresh-tokens.

Fixed

  • Fixed element integrations update matching logic where matched data is empty.
  • Fixed populateFormValues values and dynamic Twig.
  • Fixed an error with Phone number fields and countryCode.
  • Fixed an error with Phone number fields and countryName.
  • Fixed incorrect foreign key constraints for payments on new Formie installs.
  • Fixed required Agree fields not validating correctly.

Removed

  • Removed multi and limitOptions for File Upload fields for GraphQL (not applicable).

2.1.17

29 May 04:41
Compare
Choose a tag to compare

Changed

  • Ensure that sessions exists when calling formie/forms/refresh-tokens.

Fixed

  • Fixed element integrations update matching logic where matched data is empty.
  • Fixed populateFormValues values and dynamic Twig.
  • Fixed an error with Phone number fields and countryCode.
  • Fixed an error with Phone number fields and countryName.

3.0.0-beta.12

27 May 10:01
Compare
Choose a tag to compare
3.0.0-beta.12 Pre-release
Pre-release

Added

  • Phone fields now include countryCode and countryName in their value when the value is JSON.

Changed

  • Removed unused e.target from Repeater addRow() JS function.
  • Updated English translations.
  • Updated reCAPTCHA Enterprise’s Secret API Key plugin setting.

Fixed

  • Fixed Entry element integrations not using their section’s default entry status when enabled wasn’t mapped.
  • Fixed country-enabled Phone fields not having their generated value set correctly.
  • Fixed an error with Phone number fields and countryCode.
  • Fixed options-based fields and their options value when queried via GraphQL.
  • Fixed integration field selects not synchronizing with field changes.
  • Fixed showing field when none for integration options.
  • Fixed Sub-Fields in Nested fields not working correctly for integrations.
  • Fixed Phone field front-end styling for country code.
  • Fixed checkbox select inputs not retaining their values.

2.1.16

27 May 09:56
Compare
Choose a tag to compare

Added

  • Phone fields now include countryCode and countryName in their value when the value is JSON.

Changed

  • Removed unused e.target from Repeater addRow() JS function.
  • Updated English translations.
  • Updated reCAPTCHA Enterprise’s Secret API Key plugin setting.

Fixed

  • Fixed Entry element integrations not using their section’s default entry status when enabled wasn’t mapped.
  • Fixed country-enabled Phone fields not having their generated value set correctly.

3.0.0-beta.11

20 May 11:03
Compare
Choose a tag to compare
3.0.0-beta.11 Pre-release
Pre-release

Added

  • Added error logging when Captcha integration settings fail.

Changed

  • Allow form. setPageSettings() to use either the zero-based index of the page, or the page handle.
  • Field Layout Pages now auto-generate a handle based on the label of the page.
  • Improved error message for integration refresh tasks.

Fixed

  • Fixed disabled Sub-Field fields from triggering validation.
  • Fixed an error with Loqate Address autocomplete.
  • Fixed clone icon for cloning fields in the form builder.
  • Fixed custom Theme Config classes not applying correctly in JS when multiple classes are used.
  • Fixed form.setPageSettings() method.
  • Fixed front-end validation not including aria-valid attributes.
  • Fixed an error where Theme Config custom field error’s weren’t working.
  • Fixed Webhook and Slack Webhook integrations with correct response handling.
  • Fixed a type error for integrations getFieldMappingValues().
  • Fixed an error with Salesforce integration.
  • Fixed emoji support for Integrations.
  • Fixed an error when adding existing fields to a form.

2.1.15

20 May 10:57
Compare
Choose a tag to compare

Fixed

  • Fixed an error with options fields where the incorrect ID was being generated when an option value contained special characters.
  • Fixed an error when querying submissions by userId and not just a single ID.
  • Fixed options-based fields not trimming their option value.

1.6.42

20 May 11:05
Compare
Choose a tag to compare

Fixed

  • Fix an error when triggering an integration where the tokenId has become invalid.

3.0.0-beta.10

07 May 15:05
Compare
Choose a tag to compare
3.0.0-beta.10 Pre-release
Pre-release

Added

  • Added disabled property to GraphQL Dropdown field interface
  • Added Formie::EVENT_MODIFY_TWIG_ENVIRONMENT event to modify the Twig Sandbox for variable parsing.
  • Added Variables::EVENT_REGISTER_VARIABLES event to register your own.
  • Added Field::getValueForVariable() to allow fields to handle logic for variables.
  • Added Field::getValueForCondition() for handling serialization for condition evaluation.
  • Added Field::getValueForEmailPreview() for fields to define their own preview for email notifications.
  • Added disabled property to GraphQL Dropdown field interface
  • Added useMultipleFields for Name field for GraphQL

Changed

  • Improve performance when parsing variables for email notifications.
  • Options fields (Dropdown, Checkboxes, Radio Buttons) now honour the “Email Notification Value” when using field values as variables

Fixed

  • Fixed an error when using dynamic Dropdown options.
  • Fixed a PHP 8 error.
  • Fixed paths for Craft Cloud. (thanks @timkelty).
  • Fixed Repeater fields not retaining their values correctly.
  • Fixed Form export (from the Form element index) not using custom Formie export logic.
  • Fixed Name and Address sub-field conditions not working correctly.
  • Fixed an error when importing forms, where custom field content existed while the custom fields themselves didn’t.
  • Fixed Group/Repeater field conditions not working correctly when complex rules were created.
  • Fixed an error for Name fields and defineValueAsString().
  • Fixed nested fields not working correctly with field conditions.
  • Fixed an error with File Upload, client-side validation.
  • Fixed Date field layout issues in Safari and Mobile Safari.
  • Fixed an error with File Upload and MariaDB.
  • Fixed an error with element integrations where no custom fields are present.
  • Fixed an error when running Entry element integrations.
  • Fixed an error with Name Prefix field options not working.
  • Fixed an error for "Unique Value" fields.
  • Fixed a JS error for client-side validation with Theme Config resetClasses set.
  • Fixed Entry element integrations not working for Craft 5 entry type changes.
  • Fixed resolved nested field’s form.
  • Fixed GraphQL input types.
  • Fixed an error with Date field variables.
  • Fixed an error with Postgres installs.
  • Fixed an error with Campaign integration lists.
  • Fixed an error for some captchas when refreshing JS tokens.
  • Fixed default “Contact Form” stencils not working for new installs.

2.1.14

07 May 14:42
Compare
Choose a tag to compare

Added

  • Added disabled property to GraphQL Dropdown field interface
  • Added Formie::EVENT_MODIFY_TWIG_ENVIRONMENT event to modify the Twig Sandbox for variable parsing.
  • Added Variables::EVENT_REGISTER_VARIABLES event to register your own.

Fixed

  • Fixed an error when using dynamic Dropdown options
  • Fixed a PHP 8 error.
  • Fixed paths for Craft Cloud. (thanks @timkelty).
  • Fixed Repeater fields not retaining their values correctly.
  • Fixed Form export (from the Form element index) not using custom Formie export logic.
  • Fixed Name and Address sub-field conditions not working correctly.
  • Fixed an error when importing forms, where custom field content existed while the custom fields themselves didn’t.
  • Fixed Group/Repeater field conditions not working correctly when complex rules were created.