This repository has been archived by the owner on Apr 3, 2024. It is now read-only.
Releases: rhythmagency/formulate
Releases · rhythmagency/formulate
Release v1.5.4
Since version 1.5.3, these changes have been made:
- Client-Side Only Mandatory Validation The mandatory validation can now be configured so that it only validates on the client side (i.e., in the browser). This is configured on the node for your validation and is distinct from the
enableServerSideValidation
setting in~/config/formulate/submissions.config
.
Release v1.5.3
Since version 1.5.2, these changes have been made:
- Email Headers You can now edit
~/config/formulate/email.config
to specify headers to add to your emails sent by the "Email" handler. For example, an "X-Mailer" or a "Message-ID" header. Thanks to @drooks for implementing this. - Email Format Emails sent by the "Email" handler will now be sent with both HTML and plain text formats.
Release v1.5.2
Release v1.5.1
Since version 1.5.0, these changes have been made:
- Don't Store reCAPTCHA The value submitted with reCAPTCHA fields will no longer be stored to the database on submissions. Thanks to Angelo for reporting this issue.
Release v1.5.0
Since version 1.4.1, these changes have been made:
- Server Side Validation Validations have so far been client side. This enables them server side (useful to avoid malicious submissions that bypass JavaScript). You can disable server side validations in the
~/config/formulate/submissions.config
file by settingenableServerSideValidation="false"
(useful if you are using conditional fields with some potentially hidden fields being required). If you have any custom validations that implementIValidationKind
, you'll need to implement the methodIsValueValid
, which you can see an example of here (simply return true if you don't want to worry about validating server side): https://github.com/rhythmagency/formulate/blob/303118e6f5a546a835eb979432bcf8460b2f4eb0/src/formulate.app/Validations/Kinds/Mandatory/ValidationMandatory.cs#L104
Release v1.4.1
Since version 1.4.0, these changes have been made:
- Category field property will be included in the Angular model
- Fix mandatory validation for Checkbox List - fixes #85
Release v1.4.0
Since version 1.3.8, these changes have been made:
- Output Field Alias The field alias will now be output in the DOM as a CSS class (e.g., for a field with an alias of "firstName", a CSS class will be attached as "formulate__field-alias--first-name"). Makes custom styling easier.
- Delete Form Submissions You can now delete form submissions (see below animated GIF).
Release v1.3.8
Since version 1.3.7, these changes have been made:
- Fixed Build NuGet package restore will now work when running the build.bat file.
- Entity Picker Help When selecting the wrong type of entity in an entity picker (e.g., the configured form picker), a notification will now display with guidance to help make the correct selection.
- Dialog Styles Minor style improvements in the configured form picker dialog.
Release v1.3.7
Since version 1.3.6, these changes have been made:
- Grid / LeBlender The configured form picker will now work within Umbraco grid / LeBlender. Thanks to @JJCLane
- Visual Studio 2017 The Grunt process has been updated to work with Visual Studio 2017. Going forward, code that incorporates new C# syntax that only builds in Visual Studio 2017 will be accepted.
Release v1.3.6
Since version 1.3.5, these changes have been made:
Additional logging added