v4.1.0

• Laravel Boost guidelines.

v4.0.0

• Statamic 6 support
• Livewire 4 support
• Fix pagination ?page query string when using custom query sting.

v3.1.4

• Fix: Correctly decode URL encoded values

v3.1.3

• Fixed: Lazyload placeholder view was always the default (the parameter didn't get through).

v3.1.2

• Fixed: Pagination was not reset when the user was using the "Clear filter" button or when removing an option using LfTags.

v3.1.1

• Significantly improve the performance of filter option counts.

v3.1.0

• Added support for the dictionary field.
  You can now use the built-in or any custom Dictionaries as a filter.
• Fixed ordering for the entries fieldtype.

v3.0.1

• FIX Display the key of a select field when the label is not set.

v3.0.0

✨ What's New

• Upgraded to Tailwind v4
  This makes customizing the theme, especially for minor color changes, much easier. If you're updating from a v2.x version, please check the installation guide for a required configuration change.

• New Advanced Filters with Alpine.js
  We've added new "advanced" select and checkbox filters! They are ideal for horizontal layouts, offer consistent styling across different platforms, and can be made searchable. See them in action on the horizontal demo page.

• New Toggle Filter
  The new Toggle Filter allows you to create filters with preset values that your users can simply turn on or off.

🚀 Improvements & Fixes

• Added a placeholder property to all applicable filters.
• Upgraded the core dependency to marcorieser/statamic-livewire v5.0.0.
• Made several accessibility improvements.
• Fixed various minor bugs.

v2.7.0

Added support for entries field.

You can add use an entries relationship field as a filter. The published entries from all associated collections will appear as options.

When using multi-site and a Statamic entries field to filter your entries, Livewire Filters defaults to using each entry’s origin ID. This aligns with Statamic’s behavior, where the origin acts as the source of truth unless the field has been localized. We believe this is the most common use case, as it preserves relationships while allowing the associated entry to be translated.

If you are localizing the entries field itself and want to change this behavior, set the use_origin_id_for_entries_field option to false in the config file. This will make Livewire Filters use the entry ID from the current site for filtering instead.