Skip to content

Releases: verbb/formie

1.2.23

16 Oct 00:29
Compare
Choose a tag to compare

Changed

  • File upload fields now render links to their control-panel assets in email templates, in addition to being attachments.

Fixed

  • Fixed group fields displaying incorrectly in email previews.
  • Fixed group fields not checking for nested field’s hasLabel attribute in email content.
  • Fixed repeater fields not checking for nested field’s hasLabel attribute in email content.
  • Fixed form settings now saving correctly when users with limited permissions save forms.
  • Fixed an error with entry integrations and author.
  • Element integrations now correctly translate Formie fields to Craft fields.

1.2.22

15 Oct 03:32
Compare
Choose a tag to compare

Added

  • Added descriptionHtml for GraphQL querying Agree fields’ description.
  • Table, Repeater and Rich Text JS now provide access to their JS classes on field DOM elements.
  • Repeater field’s JS now triggers an init event.

Fixed

  • Fix integrations throwing errors when opting-out of the integration (through events or opt-in field).
  • When Validate When Typing is set on a form, ensure that the global form error message is removed after errors are fixed (when typing).
  • Fix Agree fields’ description being incorrectly formatted when calling through GraphQL.

1.2.21

13 Oct 00:58
Compare
Choose a tag to compare

Added

  • Added enableUnloadWarning plugin setting, to control the “unload” warning for front-end forms. This warning is used to prompt users their form has changed for good UX.
  • Added renderJs and renderCss options to renderForm(), to allow for enable/disable of resources on specific render calls.

Fixed

  • Fixed potential error with Agree field descriptions.
  • Fixed incorrectly exporting all form submissions site-wide when a specific form’s submissions were selected.
  • Fixed submission exports not resolving the content table correctly.
  • Fixed submission element index not showing available custom fields to customise with.

1.2.20

12 Oct 13:09
Compare
Choose a tag to compare

Added

  • Added more logging for webhook integrations when troubleshooting.
  • Added siteId to submissions. Now makes it possible to know which site a submission was made on.
  • Added multi-site support for submissions.
  • Allow fields in submissions to be searchable.
  • Added “Error Message Position” option for forms to control where form-wide errors are shown.
  • Twig template code can now be included inside a HTML field.
  • Setup template roots to allow for much easier template overrides.
  • Allow form includes to be overridden individually.
  • Allow field hooks to override field settings.
  • Added fui-next to all forward-progressing submit buttons, except the final submit button, for multi-page forms.
  • Added inputAttributes and containerAttributes for submit buttons.
  • Added defaultLabelPosition and defaultInstructionsPosition to plugin settings for site-wide defaults.
  • Added time label to date field.
  • Address sub-fields can now be set to hidden. Assists with using only autocomplete field.
  • Added User element integration.

Changed

  • Integration settings can now be viewed read-only when allowAdminChanges is false.
  • Agree field’s description now uses HTML content.
  • Re-organised front-end form includes.
  • Extract submit button front-end template to its own include, to allow easier overriding.
  • Recipients field label position is set to “Hidden” by default (because the default field is set to hidden).
  • Address fields can now have only the autocomplete block enabled.
  • Forms now no longer forces novalidate. HTML5 validation will trigger when Formie’s JS validation is not triggered.

Fixed

  • Fixed file upload fields in nested fields not attaching to email notifications.
  • Fixed fields in nested fields showing in email notifications when their field settings don't allow it.
  • Fixed an error with email notification preview, preventing CSS bleeding into the control panel.
  • Fixed webhook integrations not always using the per-form defined Webhook URL.
  • Fixed Formie's front-end templates, as Sass variables not being able to be overwritten. (thanks @leevigraham).
  • Fixed submission field data not exporting, when exporting from “All Forms”.
  • Fixed “Site Name” for variable picker reflect the site the submission was made on.
  • Fixed attributes and custom fields for submissions not being able to be searched.
  • Fixed rich text content not having access to all available fields in the variable picker.
  • Fixed a few issues with Address field and auto-complete behaving inconsistently with other sub-fields.
  • Fixed autocomplete field for Address fields not showing for submissions.
  • Remove <small> HTML elements from instructions for front-end templates. Produced invalid HTML.

1.2.19

26 Sep 07:54
Compare
Choose a tag to compare

Added

  • Allow Redirect URL for a form's settings to contain Twig.
  • Added Submission ID as an available variable to pick from in notifications.

Fixed

  • Fixed an error when an Ajax-enabled form's Redirect URL setting contained Twig.
  • Fixed submission variables incorrectly caching when sending multiple notifications.

1.2.18

24 Sep 23:29
Compare
Choose a tag to compare

Added

  • Added endpoint and method to payload events for integrations.

Fixed

  • Fixed serialization of phone fields for integrations.
  • Fixed being unable to modify payload in beforeSendPayload event.
  • Fixed a number of fields (checkbox, radio, agree, date, phone) where the custom error message wasn't working.
  • Fixed error when connecting with AutoPilot.
  • Fixed image uploads not attaching to email notifications for non-local volumes.
  • Ensure nested fields (group and repeater) respect MySQL table name limits. Prevents errors when saving a very long field name.
  • Fixed an error when editing a form when a user doesn’t have permission for the primary site.

1.2.17

23 Sep 09:56
Compare
Choose a tag to compare

Added

  • Added support for group fields and subfield-enabled fields (name, address) to be used as variable tags.
  • Added ability to override form settings, classes and attributes in templates.

Fixed

  • Fixed isJsonObject error for Craft 3.4.

1.2.16

22 Sep 06:25
Compare
Choose a tag to compare

Fixed

  • Fixed name field serializing non-multiple fields for integrations
  • Fixed some fields (name, date, phone) always allowing mapping for their subfields for integrations.
  • Fixed front-end submission editing not working for multi-page forms.

1.2.15

21 Sep 13:38
Compare
Choose a tag to compare

Added

  • Added status and statusId to be used in GQL mutations for submissions.

Changed

  • Refactor field serialization for integrations. Provides better support for array-like data.
  • Recipients field settings now no longer enforce unique values for options.
  • Allow table fields in field settings to add new rows with spacebar (for accessibility).
  • Switch reCAPTCHA verification servers to recaptcha.net. Hopefully to improve global reach, when access to google.com isn't allowed.

Fixed

  • Fixed checkboxes fields not serializing correctly for integrations.
  • Fixed table validation rules firing for all rules, instead of the specific defined ones per its field settings.
  • Fixed initialising multiple forms manually, with the JS API on the same page.
  • Fixed calling destroyForm in the JS API not destroying event listeners correctly.
  • Fixed integrations not saving when setting as disabled.
  • Fixed custom fields not being registered correctly.
  • Fixed submissions created via mutations in GraphQL not validating correctly.
  • Fixed submissions created via mutations in GraphQL not sending email notifications.
  • Fixed submissions created via mutations in GraphQL not triggering integrations.

1.2.14

17 Sep 13:45
Compare
Choose a tag to compare

Added

  • Added name/address support for GraphQL mutations.
  • Added Mercury CRM integration.

Changed

  • Rename Submission URL to Submission CP URL for better clarity for field variables in email notifications.

Fixed

  • Fixed Entry fields not rendering their values correctly in email notifications, when their section had no URL settings.
  • Fixed Category fields not rendering their values correctly in email notifications, when their group had no URL settings.
  • Fixed Product fields not rendering their values correctly in email notifications, when their product type had no URL settings.
  • Fixed Tag fields not rendering their values correctly in email notifications.
  • Fixed User fields not rendering their values correctly in email notifications.
  • Fixed Variant fields not rendering their values correctly in email notifications, when their product type had no URL settings.
  • Fixed incorrect validation when saving a recipients field with the display type set to hidden.