Livewire Forms Release Notes

What's new

• Add config options to control panel by @aerni in https://github.com/aerni/statamic-livewire-forms/pull/73
• Never render hidden fields by @aerni in https://github.com/aerni/statamic-livewire-forms/pull/74

What's fixed

• Bump vite from 4.5.3 to 4.5.5 by @dependabot in https://github.com/aerni/statamic-livewire-forms/pull/72
• Bump rollup from 3.29.4 to 3.29.5 by @dependabot in https://github.com/aerni/statamic-livewire-forms/pull/71

What's fixed

• Make reCAPTCHA work with lazy form components. You'll need to manually update your captcha.blade.php view to implement the fix. by @aerni in https://github.com/aerni/statamic-livewire-forms/pull/69

What's fixed

• Fix options according to changes in Statamic by @aerni in https://github.com/aerni/statamic-livewire-forms/pull/68

What's new

• Add the ability to redirect the user after form submission by @aerni in https://github.com/aerni/statamic-livewire-forms/pull/64

What's new

• Load scoped form localizations from vendor lang file by @aerni in https://github.com/aerni/statamic-livewire-forms/pull/62

What's new

• Add support for Statamic's native hide_display property as a replacement for the previously deprecated show_label property by @aerni in https://github.com/aerni/statamic-livewire-forms/pull/59

What's fixed

• Fix processing of asset fields with max_files: 1 by @aerni in https://github.com/aerni/statamic-livewire-forms/pull/60
• Some minor tweaks and improvements to views by @aerni in https://github.com/aerni/statamic-livewire-forms/pull/59
• Respect the configured Livewire namespace when creating a Livewire Forms component by @aerni in https://github.com/aerni/statamic-livewire-forms/pull/61

What's fixed

• Fix upload of assets by @aerni in https://github.com/aerni/statamic-livewire-forms/pull/57

What's fixed

• Fix issues around hidden fields by @aerni in https://github.com/aerni/statamic-livewire-forms/pull/55

Livewire Forms was rewritten from the ground up to support the latest features of Livewire 3. It is much faster and snappier and comes with notable new features, such as a wizard form type for stepped forms. Please follow the Upgrade Guide.

What's new

• Rewritten from the ground up for Livewire 3.
• Support for Statamic 5.
• Support for Laravel 11.
• New wizard form type.
• Major performance improvements.
• Conditional fields powered by Alpine.
• Self-containing field models powered by a synthesizer
• FilePond integration for the Assets field.
• Prettier commands thanks to Laravel Prompts.

Breaking changes

• Complete overhaul of the theme folder structure and its views.
• Replaced the @formSections, @formHoneypot, @formSubmit, @formErrors and @formSuccess blade directives with a global @formView directive.
• Removed the hydratedFields, submittingForm, createdSubmission, and submittedForm hooks.
• Removed the submissionCreated event.
• Removed the $HANDLE, $VIEW and $THEME component properties.
• Removed showLabel field property.

What's new

• Added support for Statamic's new spacer fieldtype. Follow these instructions on how to use it. https://github.com/aerni/statamic-livewire-forms/pull/39

What's changed

• Require Statamic 4.9

What's fixed

• Always save value of Hidden fields https://github.com/aerni/statamic-livewire-forms/pull/37

This release introduces some breaking changes that require manual adjustments of your form blueprints, views, and translations. Please follow the Upgrade Guide.

What's new

• Added support for Statamic 4 #35
• Added support for Laravel 10 #35
• Added support for native form sections #36
• Small improvements to form stubs #36

What's changed

• Dropped support for Statamic 3 #35
• Dropped support for Laravel 8 #35
• Bumped Livewire dependencies #35

What's fixed

• Fixed a Livewire diffing issue by making the wire key unique. You have to manually update your views to apply this fix.

What's breaking

• The old group: {handle} syntax has been removed in favor of native form sections
• Removed the @formFields, @formGroups, and @formGroup blade directives
• Removed the fields.blade.php, groups.blade.php, and group.blade.php views
• The translation of the display and instructions of form sections have been moved to JSON files
• The realtime validation config in the form blueprint has been moved to the blueprint's root

What's fixed

• Always save value of Hidden fields #37

What's new

• You can now override a field's rules and validationAttributes to handle more complex field models #33

What's fixed

• Improved compatibility with cache drivers that don't support large keys #32

What's new

• Added the ability to autoload field views by handle #31
• Don't submit values of conditionally hidden fields #30
• Added French translations #29
• Added support for Statamic 3.4

What's breaking

The data flow behavior introduced with PR #30 is technically a breaking change. If you rely on the values of hidden fields to be submitted, you should add always_save: true to the fields in question.

What's fixed

• Fix issue where booleans in conditions didn't evaluate as expected

What's fixed

• Prevent random swap of conditional fields. Make sure to update your field.blade.php views according to the PR. #24

What's improved

• Hide text fields with input_type: hidden #26

What's new

• Adds new createdSubmission callback #21

What's new

• Adds support for the Hidden fieldtype. It's basically a shortcut to using a text field with show: false.

What's fixed

• Fixed field conditions. This bug was introduced in v5.0.0. You should upgrade to this version to fix it.

What's improved

• Hide form groups that don't contain any visible fields. Like when using the Hidden fieldtype or conditions.
• Better alignment of checkbox and radio fields when displayed inline.

What's new

• You can now override messages like the form submit button and success message on a per form level. This is super useful, as you don't have to create a custom form component anymore to change a simple message string.

What's improved

• The validation.php language file is now merged into the messages.php file

What's breaking

• If you've published the language files, you'll have to manually migrate to the new structure. Simply publish the language files again and copy-paste the strings in question.

What's fixed

• Fixed showstopper because of accidentally changed method visibility
• Fixed form reset on submission if the form doesn't contain a captcha field

What's improved

• Improved field views by making field labels smaller when there is no instruction

What's fixed

• The captcha response is no longer saved to form submissions

What's improved

• Field property methods are now executed on demand, allowing for dynamic use. This is helpful if you change a field property like options in the hydratedFields callback.
• Make the inline_label property translatable
• Make the show, view, and wire_model_modifier properties configurable through the form blueprint
• Make the input_type property of Integer fields configurable

What's breaking

• All field property methods are now protected. If you've accessed properties using their methods like defaultProperty(), you can simply remove Property and use default() instead.
• If you've changed the view of a field through the @formField blade directive, you should remove fields., e.g. instead of 'view' => 'fields.nameInput' it should now be 'view' => 'nameInput'.

What's new

• Adds the ability to autoload custom components by form handle. Example: {{ livewire:form handle="contact" }} will load App\Http\Livewire\ContactForm.php if it exists. (#18)

Upgrade Guide

Required

• Make sure your custom components extend Aerni\LivewireForms\Http\Livewire\BaseForm

Optional

The following changes are only necessary if you want to use the new autoloading capabilities.

• Ensure your custom components end with Form, e.g. rename Contact to ContactForm.
• Change your template to use the default form component, e.g. use {{ livewire:form handle="contact" }} instead of {{ livewire:contact }}.
• You can safely remove the public string $handle property from your component.
• If you've set the $view and $theme property, exchange them with protected static $VIEW and protected static $THEME.

What's new

• Added support for the Toggle fieldtype. This is super useful for single checkbox fields like terms and conditions.

What's improved

• Labels and legends are now available for screen readers even if a field has show_label: false. This only applies to newly created themes. Feel free to copy-paste the field stubs into your existing themes.

What's fixed

• Fixed mail attachments (requires Statamic 3.3.12+)
• Fixed an issue that wouldn't let you select a new file in an asset field with max_files: 1
• Asset fields are now reset after the form has been submitted

What's new

• Required Statamic 3.3.12+

What's new

• Added support for Laravel 9

What's new

• Added support for Statamic 3.3

What's new

• Added support for field conditions. Go nuts!
• Added support for the assets fieldtype.
• Complete refactor introducing a whole bunch of new concepts and customization options like themes, components, hooks, callbacks, and more. Make sure to read the docs.

What's breaking

• Dropped support for PHP 7.4
• Changed the form parameter on the component to handle.
• The component view now defaults to default and not the handle of the form anymore. Use the view parameter on the component to use a different view.
• You now need a theme. Run php please livewire-forms:theme to create one.
• There are lots of breaking changes in the form views. Migrate your old views to the views in the theme you just created.
• There are probably other changes as well. Just make sure to read the docs and follow the instructions. It should be pretty easy to upgrade.

What's new

• Added support for Google reCAPTCHA v2.
• You can now use show_label on all fieldtypes.
• select fields now also render their instructions.

What's fixed

• Avoid name collisions when using multiple forms on the same page.

What's breaking

• Removed support for Antlers views. You can still import your form component in your Antlers views, but the form views themselves are only provided in Blade now. If you published your form views in Antlers, they will no longer work. You will need to publish the form views afresh and update the markup according to your changes.
• Multiple changes to the form views. If you published the views, you have to manually update them.

What's new

• You can now define the form view using the new view parameter.

What's improved

• The form views are now stored in their own directory views/livewire/forms. Make sure to move your existing views there.

• N/A Changelog not available.