Changelog

​

What’s Changed

• Bump aglipanci/laravel-pint-action from 2.5 to 2.6 Bumps aglipanci/laravel-pint-action from 2.5 to 2.6.
• Bump actions/checkout from 4 to 5 Bumps actions/checkout from 4 to 5.
• Fix dont show new columns in user views This PR fixes an issue where adding a new column to the table schema would then cause the column to appear in User Views. Additionally, the toggling off the column in the column dropdown would then take two clicks. Now, new columns will be toggled off if they are not in the user view. Users can always use the “Replace view” functionality if they want to show/reorder new columns.

​

What’s Changed

• Bump aglipanci/laravel-pint-action from 2.5 to 2.6 Bumps aglipanci/laravel-pint-action from 2.5 to 2.6.
• Bump actions/checkout from 4 to 5 Bumps actions/checkout from 4 to 5.
• Fix dont show new columns in user views This PR fixes an issue where adding a new column to the table schema would then cause the column to appear in User Views. Additionally, the toggling off the column in the column dropdown would then take two clicks. Now, new columns will be toggled off if they are not in the user view. Users can always use the “Replace view” functionality if they want to show/reorder new columns.

​

What’s Changed

• Bump aglipanci/laravel-pint-action from 2.5 to 2.6 Bumps aglipanci/laravel-pint-action from 2.5 to 2.6.
• Bump actions/checkout from 4 to 5 Bumps actions/checkout from 4 to 5.
• Fix dont show new columns in user views This PR fixes an issue where adding a new column to the table schema would then cause the column to appear in User Views. Additionally, the toggling off the column in the column dropdown would then take two clicks. Now, new columns will be toggled off if they are not in the user view. Users can always use the “Replace view” functionality if they want to show/reorder new columns.

​

What’s Changed

• Fix-preserveFilters-when-going-from-userView-to-PresetView Currently when using preserveFilters() on a PresetView, if a UserView with filters is selected and then the PresetView is selected, the PresetView is not highlighted. This works when you go from PresetView -> PresetView, but does not when going from UserView -> PresetView. This PR fixes this issue.

​

What’s Changed

• Fix-preserveFilters-when-going-from-userView-to-PresetView Currently when using preserveFilters() on a PresetView, if a UserView with filters is selected and then the PresetView is selected, the PresetView is not highlighted. This works when you go from PresetView -> PresetView, but does not when going from UserView -> PresetView. This PR fixes this issue.

​

What’s Changed

• Fix-preserveFilters-when-going-from-userView-to-PresetView Currently when using preserveFilters() on a PresetView, if a UserView with filters is selected and then the PresetView is selected, the PresetView is not highlighted. This works when you go from PresetView -> PresetView, but does not when going from UserView -> PresetView. This PR fixes this issue.

​

What’s Changed

• Fix Model::shouldBeStrict error Fixes an issue where adding Model::shouldBeStrict() and disabling managedDefaultViews would cause a The attribute [is_current_default] either does not exist or was not retrieved for model [Archilex\AdvancedTables\Models\UserView] as is_current_default is a subquery column only created when managedDefaultViews is enabled. This fix looks for for the attribute directly in the attributes array. In my testing this was faster than the alternative of looking at the config setting and then if managedDefaultViews is enabled to then look at the attribute.

​

What’s Changed

• Fix Model::shouldBeStrict error Fixes an issue where adding Model::shouldBeStrict() and disabling managedDefaultViews would cause a The attribute [is_current_default] either does not exist or was not retrieved for model [Archilex\AdvancedTables\Models\UserView] as is_current_default is a subquery column only created when managedDefaultViews is enabled. This fix looks for for the attribute directly in the attributes array. In my testing this was faster than the alternative of looking at the config setting and then if managedDefaultViews is enabled to then look at the attribute.

​

What’s Changed

• Fix toggleOnAllColumns with relationships Fixes an issue when toggling on all columns (Enable All), when there are columns that use dotted relationships

​

What’s Changed

• Fix toggleOnAllColumns with relationships Fixes an issue when toggling on all columns (Enable All), when there are columns that use dotted relationships

​

What’s Changed

• Fix toggleOnAllColumns with relationships Fixes an issue when toggling on all columns (Enable All), when there are columns that use dotted relationships

​

What’s Changed

• Try fix deprecation error to Str::beforeLast() I originally reported it on https://github.com/filamentphp/filament/issues/16852 If you look at Laravel’s Str class, only the beforeLast() method uses mb_strrpos() I didn’t manage to trace filament removeTableFilter() method deep enough to find a Str::beforeLast() But I manage to find it in this package removeTableFilter() method so i like to make this PR to this package 1st to see if it fix the issue for me as Sentry gives me a lot of alerts. I see that you allow $field to be null too so there is a chance$field is null and cause those deprecation errors
• Bump stefanzweifel/git-auto-commit-action from 5 to 6 Bumps stefanzweifel/git-auto-commit-action from 5 to 6.

​

New Contributors

• @ziming made their first contribution

​

What’s Changed

• Try fix deprecation error to Str::beforeLast() I originally reported it on https://github.com/filamentphp/filament/issues/16852 If you look at Laravel’s Str class, only the beforeLast() method uses mb_strrpos() I didn’t manage to trace filament removeTableFilter() method deep enough to find a Str::beforeLast() But I manage to find it in this package removeTableFilter() method so i like to make this PR to this package 1st to see if it fix the issue for me as Sentry gives me a lot of alerts. I see that you allow $field to be null too so there is a chance$field is null and cause those deprecation errors
• Bump stefanzweifel/git-auto-commit-action from 5 to 6 Bumps stefanzweifel/git-auto-commit-action from 5 to 6.

​

New Contributors

• @ziming made their first contribution

​

What’s Changed

• Try fix deprecation error to Str::beforeLast() I originally reported it on https://github.com/filamentphp/filament/issues/16852 If you look at Laravel’s Str class, only the beforeLast() method uses mb_strrpos() I didn’t manage to trace filament removeTableFilter() method deep enough to find a Str::beforeLast() But I manage to find it in this package removeTableFilter() method so i like to make this PR to this package 1st to see if it fix the issue for me as Sentry gives me a lot of alerts. I see that you allow $field to be null too so there is a chance$field is null and cause those deprecation errors
• Bump stefanzweifel/git-auto-commit-action from 5 to 6 Bumps stefanzweifel/git-auto-commit-action from 5 to 6.

​

New Contributors

• @ziming made their first contribution

​

What’s Changed

• Fix date filter This PR fixes the absolute date filter (is date, before date, after date) that broke with the recent addition to is_empty and is not empty
• Fix more than 6 or groups If a user was using more than 6 or groups in AdvancedFilters it would throw an error as there were only 6 colors to select from. This PR will now cycle through the indicator colors allow infinite or groups
• Improve support for filament minimal theme Adds support for Filament’s Minimal Theme. If you are using Filament’s Minimal Theme and have been adding css to your theme, you should be able to remove that now and just use ->minimalTheme() and the Advanced Tables’ plugin object

​

What’s Changed

• Fix date filter This PR fixes the absolute date filter (is date, before date, after date) that broke with the recent addition to is_empty and is not empty
• Fix more than 6 or groups If a user was using more than 6 or groups in AdvancedFilters it would throw an error as there were only 6 colors to select from. This PR will now cycle through the indicator colors allow infinite or groups
• Improve support for filament minimal theme Adds support for Filament’s Minimal Theme. If you are using Filament’s Minimal Theme and have been adding css to your theme, you should be able to remove that now and just use ->minimalTheme() and the Advanced Tables’ plugin object

​

What’s Changed

• Fix date filter This PR fixes the absolute date filter (is date, before date, after date) that broke with the recent addition to is_empty and is not empty
• Fix more than 6 or groups If a user was using more than 6 or groups in AdvancedFilters it would throw an error as there were only 6 colors to select from. This PR will now cycle through the indicator colors allow infinite or groups
• Improve support for filament minimal theme Adds support for Filament’s Minimal Theme. If you are using Filament’s Minimal Theme and have been adding css to your theme, you should be able to remove that now and just use ->minimalTheme() and the Advanced Tables’ plugin object

​

What’s Changed

• Implement current user view This PR brings over the currentUserView implementation which is part of beta10. the currentUserView allows the user/preset view to keep an indicator after changing the sorting/filtering/etc, helping to better indicate that the view is still active.
• Fix incorrect method naming Fixes an incorrect method naming that occurred when bringing currentUserView from beta 10 to beta 9
• Fix preset views that modifed the query This PR fixes a bug where a preset view that modifies the table query wasn’t being applied after a table filter/sort/etc. was updated.
• Bump dependabot/fetch-metadata from 2.3.0 to 2.4.0 Bumps dependabot/fetch-metadata from 2.3.0 to 2.4.0.
• Add empty filter to date operator This PR adds an “empty” and “is not empty” date filter to the date filter
• Fix is empty date filter Bug fixes

​

What’s Changed

• Fix is empty date filter Bug fixes

​

What’s Changed

• Fix is empty date filter Bug fixes

​

What’s Changed

• Bump dependabot/fetch-metadata from 2.3.0 to 2.4.0 Bumps dependabot/fetch-metadata from 2.3.0 to 2.4.0.
• Add empty filter to date operator This PR adds an “empty” and “is not empty” date filter to the date filter

​

What’s Changed

• Add empty filter to date operator This PR adds an “empty” and “is not empty” date filter to the date filter
• Bump dependabot/fetch-metadata from 2.3.0 to 2.4.0 Bumps dependabot/fetch-metadata from 2.3.0 to 2.4.0.

​

What’s Changed

• Bump dependabot/fetch-metadata from 2.3.0 to 2.4.0 Bumps dependabot/fetch-metadata from 2.3.0 to 2.4.0.
• Add empty filter to date operator This PR adds an “empty” and “is not empty” date filter to the date filter

​

What’s Changed

• Fix preset views that modifed the query This PR fixes a bug where a preset view that modifies the table query wasn’t being applied after a table filter/sort/etc. was updated.

​

What’s Changed

• Fix preset views that modifed the query This PR fixes a bug where a preset view that modifies the table query wasn’t being applied after a table filter/sort/etc. was updated.

​

What’s Changed

• Update HasViewActions.php Fixes a missing $column variable

​

What’s Changed

• Fix incorrect method naming Fixes an incorrect method naming that occurred when bringing currentUserView from beta 10 to beta 9

​

What’s Changed

• Implement current user view This PR brings over the currentUserView implementation which is part of beta10. the currentUserView allows the user/preset view to keep an indicator after changing the sorting/filtering/etc, helping to better indicate that the view is still active.

​

What’s Changed

• Improve support for multiple plugin instances If you are using multiple instances of the plugin on the same page (ie, multiple table widgets, or stacked relation managers), there can be conflicts with the userView/presetView/defaultViews when reloading the page. The problem is that the userView/presetView are stored in properties, which are then set in the query string through Livewire’s #[Url] attribute. Normally this is fine since there is usually only one instance of the plugin on a page at one time. However, when there are multiple instances, as you switch between different userViews/presetViews, the last view is what is stored in the url. Then when you reload the page, since those values are present in the url, livewire sets the properties and then plugin tries to load those views in each instance which overrides whatever was stored in the session. This PR introduces a hasMultipleInstances() method that you can set to false when the plugin is being used multiple times on the same page. This will basically set the userView and presetView properties to null before loading the page which will force it to fall back to using the view stored in the session, which is unique per instance. To use it, just add: php public function hasMultipleInstances(): bool { return false; } to all the List/Manage/Widget classes that are being loaded on the same page.
• Improve support for multiple trait instances Add support for #376 for beta 3.10

​

What’s Changed

• Improve support for multiple plugin instances If you are using multiple instances of the plugin on the same page (ie, multiple table widgets, or stacked relation managers), there can be conflicts with the userView/presetView/defaultViews when reloading the page. The problem is that the userView/presetView are stored in properties, which are then set in the query string through Livewire’s #[Url] attribute. Normally this is fine since there is usually only one instance of the plugin on a page at one time. However, when there are multiple instances, as you switch between different userViews/presetViews, the last view is what is stored in the url. Then when you reload the page, since those values are present in the url, livewire sets the properties and then plugin tries to load those views in each instance which overrides whatever was stored in the session. This PR introduces a hasMultipleInstances() method that you can set to false when the plugin is being used multiple times on the same page. This will basically set the userView and presetView properties to null before loading the page which will force it to fall back to using the view stored in the session, which is unique per instance. To use it, just add: php public function hasMultipleInstances(): bool { return false; } to all the List/Manage/Widget classes that are being loaded on the same page.

​

What’s Changed

• Fix hiding view manager and quick save when in favorites bar This PR fixes hiding the view manager and quick save per resource/page when they are in the favorites bar. Previously showing/hiding per resource/page only worked when it was they were in the table.

​

What’s Changed

• Fix hiding view manager and quick save when in favorites bar This PR fixes hiding the view manager and quick save per resource/page when they are in the favorites bar. Previously showing/hiding per resource/page only worked when it was they were in the table.

​

What’s Changed

• Fix hiding view manager and quick save when in favorites bar This PR fixes hiding the view manager and quick save per resource/page when they are in the favorites bar. Previously showing/hiding per resource/page only worked when it was they were in the table.

​

What’s Changed

• Replace hardcoded tenant ids

​

What’s Changed

• Replace hardcoded tenant ids

​

What’s Changed

• Replace hardcoded tenant ids

​

What’s Changed

• Update README.md
• Update default view translations

​

What’s Changed

• Update default view translations

​

What’s Changed

• Update README.md

​

What’s Changed

• Improve resetting view from view manager

​

What’s Changed

• Persist current view when persistActiveView is enabled

​

What’s Changed

• Feature advanced indicators
• initial fixes
• Advanced indicators beta readme
• Update README.md
• Improvements Better error messaging, refactor class names, fix bug when resetting form from filter form
• Update indicators.blade.php This PR fixes an issue when you have Advanced Indicators enabled globally, but are not using the AdvancedTables trait on a specific resource or page.
• Feature Multi-Sort This PR introduces Multi-Sort to Advanced Tables. Docs here: https://filamentphp.com/plugins/kenneth-sese-advanced-tables#multi-sort-beta
• Update translations
• Fix multi sort column labels Fixes the column labels for the multi-sort dropdown and picker
• Fix advanced indicators using filter form section Adds support for filter forms that use Sections
• Update updated filament method Filament v3.2.133 updated the getFilters() method. This PR updates this method to keep it compatible and makes 3.2.133 the minimum version going forward.
• Update composer.json
• Improve compatibility between default view and beta 10

​

What’s Changed

• Allow customizable default icon

​

What’s Changed

• Default View tweaks

​

What’s Changed

• Feature user defined default views

​

What’s Changed

• Fix type enable skeleton loading

​

What’s Changed

• Enable skeleton loading on pagination

​

What’s Changed

• Update composer.json

​

What’s Changed

• Laravel 12
• Update readme for laravel 12

​

What’s Changed

• Better support for Record Finder Pro plugin This PR adds better support for Ralph’s Record Finder Pro plugin using the github theme.
• Fix calling methods directly In some places I was calling action methods directly instead of as a property as recommended. This PR updates those actions
• Prevent additional requests when using deferred filters with advanced filters When using Filament’s ->deferredFilters() method along with AdvancedFilters, a request was being sent to the server each time an input was changed. This was specifically noticable with multi selects. This PR prevents those additional requests being sent over the wire until Apply is clicked.
• Move loading overlay from booted to registered Having the loading overlay in the booted method appears to cause issues when calling filament(). This PR moves this logic to the registered method to make sure the configuration is applied after the application is fully booted.
• Allow view manager and quick save to be configured per page This PR allows the View Manager and Quick Save to be configured per page. If you would like to disable either or both on a certain page/widget/relation manager by overriding the viewManagerIsEnabled() or quickSaveIsEnabled() methods. See the docs for additional information.
• Bump dependabot/fetch-metadata from 2.2.0 to 2.3.0 Bumps dependabot/fetch-metadata from 2.2.0 to 2.3.0.
• Bump aglipanci/laravel-pint-action from 2.4 to 2.5 Bumps aglipanci/laravel-pint-action from 2.4 to 2.5.
• Fix advanced filters when using nested relationships with options When using AdvancedFilters with a SelectFilter or TextFilter and a dotted relationship along with the ->options() method, the query would default to the id column instead of the specified key. This PR fixes this issue. Closes #317

​

What’s Changed

• Clear table search when enabling When clicking “default” the table search was not being cleared. This PR fixes that behavior.

​

What’s Changed

• Bump min filament version

​

What’s Changed

• Better support for Record Finder Pro plugin This PR adds better support for Ralph’s Record Finder Pro plugin using the github theme.
• Fix calling methods directly In some places I was calling action methods directly instead of as a property as recommended. This PR updates those actions
• Prevent additional requests when using deferred filters with advanced filters When using Filament’s ->deferredFilters() method along with AdvancedFilters, a request was being sent to the server each time an input was changed. This was specifically noticable with multi selects. This PR prevents those additional requests being sent over the wire until Apply is clicked.
• Move loading overlay from booted to registered Having the loading overlay in the booted method appears to cause issues when calling filament(). This PR moves this logic to the registered method to make sure the configuration is applied after the application is fully booted.
• Allow view manager and quick save to be configured per page This PR allows the View Manager and Quick Save to be configured per page. If you would like to disable either or both on a certain page/widget/relation manager by overriding the viewManagerIsEnabled() or quickSaveIsEnabled() methods. See the docs for additional information.
• Bump dependabot/fetch-metadata from 2.2.0 to 2.3.0 Bumps dependabot/fetch-metadata from 2.2.0 to 2.3.0.
• Bump aglipanci/laravel-pint-action from 2.4 to 2.5 Bumps aglipanci/laravel-pint-action from 2.4 to 2.5.
• Fix advanced filters when using nested relationships with options When using AdvancedFilters with a SelectFilter or TextFilter and a dotted relationship along with the ->options() method, the query would default to the id column instead of the specified key. This PR fixes this issue. Closes #317

​

What’s Changed

• Fix calling methods directly In some places I was calling action methods directly instead of as a property as recommended. This PR updates those actions
• Prevent additional requests when using deferred filters with advanced filters When using Filament’s ->deferredFilters() method along with AdvancedFilters, a request was being sent to the server each time an input was changed. This was specifically noticable with multi selects. This PR prevents those additional requests being sent over the wire until Apply is clicked.
• Move loading overlay from booted to registered Having the loading overlay in the booted method appears to cause issues when calling filament(). This PR moves this logic to the registered method to make sure the configuration is applied after the application is fully booted.
• Allow view manager and quick save to be configured per page This PR allows the View Manager and Quick Save to be configured per page. If you would like to disable either or both on a certain page/widget/relation manager by overriding the viewManagerIsEnabled() or quickSaveIsEnabled() methods. See the docs for additional information.
• Bump dependabot/fetch-metadata from 2.2.0 to 2.3.0 Bumps dependabot/fetch-metadata from 2.2.0 to 2.3.0.
• Bump aglipanci/laravel-pint-action from 2.4 to 2.5 Bumps aglipanci/laravel-pint-action from 2.4 to 2.5.
• Fix advanced filters when using nested relationships with options When using AdvancedFilters with a SelectFilter or TextFilter and a dotted relationship along with the ->options() method, the query would default to the id column instead of the specified key. This PR fixes this issue. Closes #317

​

What’s Changed

• Better support for Record Finder Pro plugin This PR adds better support for Ralph’s Record Finder Pro plugin using the github theme.

​

What’s Changed

• Improve skeleton loader css class target Previously, the skeleton loader targeted the fi-ta-text class, but with custom columns with custom blade files, this class might not be there. This switches to targeting the fi-ta-col-wrp class.

​

What’s Changed

• Improve skeleton loader css class target Previously, the skeleton loader targeted the fi-ta-text class, but with custom columns with custom blade files, this class might not be there. This switches to targeting the fi-ta-col-wrp class.

​

What’s Changed

• Improve loading targets for skeleton overlay This PR better targets table events so that forms in modals and slideovers don’t trigger the skeleton loader.

​

What’s Changed

• Improve loading targets for skeleton overlay This PR better targets table events so that forms in modals and slideovers don’t trigger the skeleton loader.

​

What’s Changed

• Fix toggle on all columns with nested relationships This PR fixes a bug with the recently introduced Enable All in reorderable columns that would set nested arrays to true. This PR maintains the nested arrays and recursively sets the value to true.

​

What’s Changed

• Fix toggle on all columns with nested relationships This PR fixes a bug with the recently introduced Enable All in reorderable columns that would set nested arrays to true. This PR maintains the nested arrays and recursively sets the value to true.

​

What’s Changed

• Improvement toggle on all columns This PR adds the ability to toggle on all the hidden columns at once. You may display the link as a button using the ->reorderableColumnsDisplayEnableAllAsIcon() method and you can configure the icon using the ->enableAllIcon() method
• Feature table loading overlay This PR introduces a new table skeleton overlay to give your users more feedback when their tables are loading. This can be enabled by adding the ->tableLoadingOverlay() method to the plugin object.

​

What’s Changed

• Hungarian translations
• Improvement toggle on all columns This PR adds the ability to toggle on all the hidden columns at once. You may display the link as a button using the ->reorderableColumnsDisplayEnableAllAsIcon() method and you can configure the icon using the ->enableAllIcon() method
• Feature table loading overlay This PR introduces a new table skeleton overlay to give your users more feedback when their tables are loading. This can be enabled by adding the ->tableLoadingOverlay() method to the plugin object.

​

New Contributors

• @borex made their first contribution

​

What’s Changed

• Update updated filament method Filament v3.2.133 updated the getFilters() method. This PR updates this method to keep it compatible and makes 3.2.133 the minimum version going forward.

​

What’s Changed

• Fix advanced indicators using filter form section Adds support for filter forms that use Sections

​

What’s Changed

• Fix multi sort column labels Fixes the column labels for the multi-sort dropdown and picker

​

What’s Changed

• Update translations

​

What’s Changed

• Fix for persisting column searches This PR fixes an issue where the table search or column search wouldn’t be persisted when a UserView was activated.
• Improve handling of updated columns This PR fixes an Undefined array key error that would occur when a user would save a view based on a previously saved view that had column sorting, but that sorted column had later been renamed by the developer.
• Show loading indicator when toggling reorderable columns Show loading indicator when toggling reorderable columns
• Add approve authorize and policy The PR adds an authorization gate and policy for User View approval in the UserView resource
• Hungarian translations
• Feature Multi-Sort This PR introduces Multi-Sort to Advanced Tables. Docs here: https://filamentphp.com/plugins/kenneth-sese-advanced-tables#multi-sort-beta

​

New Contributors

• @borex made their first contribution

​

What’s Changed

• Add approve authorize and policy The PR adds an authorization gate and policy for User View approval in the UserView resource

​

What’s Changed

• Show loading indicator when toggling reorderable columns Show loading indicator when toggling reorderable columns

​

What’s Changed

• Improve handling of updated columns This PR fixes an Undefined array key error that would occur when a user would save a view based on a previously saved view that had column sorting, but that sorted column had later been renamed by the developer.

​

What’s Changed

• Fix for persisting column searches This PR fixes an issue where the table search or column search wouldn’t be persisted when a UserView was activated.

​

What’s Changed

• Update indicators.blade.php This PR fixes an issue when you have Advanced Indicators enabled globally, but are not using the AdvancedTables trait on a specific resource or page.

​

What’s Changed

• Improvements Better error messaging, refactor class names, fix bug when resetting form from filter form

​

What’s Changed

• Update README.md

​

What’s Changed

• Update README.md
• Update README.md

​

What’s Changed

• initial fixes
• Advanced indicators beta readme

​

What’s Changed

• Update README.md

​

What’s Changed

• Feature advanced indicators

​

What’s Changed

• fix user view resource with multi tenancy This PR fixes an issue with loading the UserViewResource when using multi-tenancy but with ->tenancyEnabled(false). This also deprecates ->tenancyEnabled() and replaces it with ->scopeToTenancy().

​

What’s Changed

• Fix typo in docs Fixes a typo on the ->favoritesBarLoadingIndicator() method in the documentation example.
• Add support for Ralphs Record Finder plugin This PR adds support for the Record Finder plugin

​

New Contributors

• @blazerunner44 made their first contribution

​

What’s Changed

• Remove tailwind import This PR removes the unneeded tailwind import

​

What’s Changed

• Reset currentPresetView when resetting table This PR resets the currentPresetView property when resetting the table. This property is still experimental and could go away in the future and handled in a different way so use with caution.

​

What’s Changed

• Fix filter indicators with custom filament filters inside advanced filters This PR fixes filter indicators when using custom Filament filters inside of Advanced Tables. Prior to this PR, if you were using a custom filter with multiple form fields (think a date range filter) inside of Advanced Filters, a duplicate indicator would be displayed for each field even if it should only display one indicator. And if your custom filter was configured to show multiple indicators (ie, one for each field), then it would only repeat the first indicator. This PR fixes these issues.

​

What’s Changed

• Add searchable functionality to SelectFilter https://github.com/filamentphp/filament/pull/14263

​

What’s Changed

• Fix resetTable (for real this time) Sorry…named the method wrong.

​

What’s Changed

• Revert “Fix resetTable” This reverts commit 074c3f375c8621f99ae31826591a607f51d5cc40.

​

What’s Changed

• Fix resetTable This PR fixes an issue where the table wasn’t properly being reset, which could cause Filament tabs to be out of sync with the request.

​

What’s Changed

• Fix saving user views with multiple columns When saving a UserView with large amountsof columns and/or long column names, php will enforce it’s own ordering algorithm for storing the array keys. This can cause the column order to be incorrect when saving the view and thus activating a UserView can have the wrong column order. This PR will now store column order as an associative array so that the appropiate order will be maintained. Existing views will continue to work and any new views will be saved with the new format. In v4 I will provide a migration to update your existing user views.
• Improve numeric filter with aggregate relationships When using aggregate relationships (products_count) the Numeric Filter wouldn’t included null results. For example, using the Numeric Filter to filter for less than 2 products, would not return results with null. This PR improves this handling.
• Hide or show column based on table layout This PR adds better support for grid layout, specifically for disabling column ordering when a table is in grid layout as this doesn’t have any affect on the table. This is particulary useful when using the Table Layout Toggle Plugin.

​

What’s Changed

• Fix filter labels with html If you are using this trick to show a tooltip in a table column header, the html would be rendered in the filter and it’s indicator. This PR applies strip_tags() to prevent this.
• Feature: Add loading indicator to favorites bar This PR adds the option to show an loading indicator in the favorites bar. This is especially helpful with large tables that take a while to switch between views. You may show a loading indicator when switching between views by using the favoritesBarLoadingIndicator() method: php AdvancedTablesPlugin::make() ->favoritesBarLoadingIndictor()

​

What’s Changed

• Add initial currentPresetView concept This PR adds a new currentPresetView property. Since activePresetView is reset when the table is changed which can cause unintended side effects when us activePresetView to determine settings like grouping. This concept is new and will be improved / changed over time. Use at your own risk.

​

What’s Changed

• Convert relative date values to ints This PR fixes an ocassional issue when using the relative date filter (ie. in the next 2 days) where the value was being passed as a string. This PR ensures the values are ints.

​

What’s Changed

• Fix aggregate query for postgres This PR fixes the aggregate query when used with belongs to many relationships in postgres.

​

What’s Changed

• Fix managed user views when using uuids for users Fixes #306

​

What’s Changed

• Add support for belongs to many aggregate relationships with Advanced Filter This PR adds support for BelongsToMany aggregate relationships with AdvancedFilter.
• Fix advanced filter block picker with table polling Fixes an issue where the block picker dropdown would be closed when table polling was enabled

​

What’s Changed

• Improve reorderable columns This PR fixes an issue where reorderable columns wasn’t saving data in the correct array format. While the issue doesn’t appear to have affected reorderable columns in the UI, having a consistent data set will prevent future issues. Since the inconsistent array data was also saved to the DB when creating a UserView, this PR also normalizes the array that is returned from the DB so it’s consistent through the package. A migration will be provided at a later date to fix the database entries and avoid the additional method call to normalize the data. This PR also introduces caching on the getOrderedToggledColumnsFromPresetView() method to improve performance.

​

What’s Changed

• Adjust expand button top distance Adjusts the top distance for the absolute positioned expand button when using Advanced Filters to better align with the Reset button

​

What’s Changed

• Add additional filter css selectors This PR adds additional css selectors to the filter container and operators
• Bump dependabot/fetch-metadata from 2.1.0 to 2.2.0 Bumps dependabot/fetch-metadata from 2.1.0 to 2.2.0.

​

What’s Changed

• Add default reordering icons

​

What’s Changed

• Fix clipped view manager badge count Fixes an issue where the view manager badge count would be clipped when it was in the favorites bar.

​

What’s Changed

• Fix-overflowing-user-views-in-favorites-bar Fixes an issue where user views would overflow on screens larger than sm: when wider than the container.

​

What’s Changed

• Fix loading preset view in view manager Fixes #295

​

What’s Changed

• Fix incorrect button size property for Table Builder users Fixes #292
• Fix page resetting on refresh Fixes #291 This PR fixes a bug where the page would reset back to the first page when you had a presetView or userView loaded and refreshed the page. Now, the page will be maintained on refresh.

​

What’s Changed

• Scope View Manager to class This PR fixes an issue where the view manager would be shown multiple times when using AdvancedTables on multiple tables that are in multiple form tabs.

​

What’s Changed

• Feature: Allow View icons to be hidden in the View Manager

​

What’s Changed

• Replace hardcoded ‘id’ for ->getKeyName() for custom key names

​

What’s Changed

• Fix for using actions when using a Filament SelectFilter with a relationship inside of AdvancedFilters Fixes #279

​

What’s Changed

• Feature: Add Is Next… and Is Last… date filters This PR adds new Is Next and Is Last date filters for Advanced Filters allowing you to filter dates like “is last month” or “is next year”. Using the filters will set a date range between the start and end of whatever unit is chosen

'is_next' => [
    'indicator' => 'is next',
    'option' => 'is next',
],

'is_last' => [
    'indicator' => 'is last',
    'option' => 'is last',
],

​

What’s Changed

• Remove forgotten ray Sorry!

​

What’s Changed

• Feature allow view manager to be displayed as button By default, View Manager is displayed as a icon button. You may display it as a button with a label with additional options available as well: php AdvancedTablesPlugin::make() ->viewManagerButton(label: 'Views') ->viewManagerButtonSize('lg') ->viewManagerButtonOutlined() ->viewManagerIconPosition(IconPosition::After)
• Feature: Allow tenancy to be disabled If you are using multi-tenancy in your app, but would prefer User Views and Preset Views to not be scoped to each tenant (i.e. a user’s views would be the same regardless of which tenant they are in), you may disable multi-tenancy in the plugin by passing false to the ->tenancyEnabled() method: php AdvancedTablesPlugin::make() ->tenancyEnabled(false)
• Improve resetTable method
• Fix bug with custom filters and indicators
• Bump dependabot/fetch-metadata from 2.0.0 to 2.1.0 Bumps dependabot/fetch-metadata from 2.0.0 to 2.1.0.

​

What’s Changed

• Fix for using ->hidden() and ->visible() methods on filters in Advanced Filter Fixes a bug where ->visible() ->hidden() were not being applied when a filter was defined inside the ->filters() method of Advanced Filter.
• Update icon name from reorderingIcon() to reorderIcon()

​

What’s Changed

• Improvement: allow reorderable columns icons to be configured

​

What’s Changed

• Fix select filter with relationships after filament 3.2.63 update

​

What’s Changed

• Fix relationship declaration after Filament 3.2.63 update
• Bump aglipanci/laravel-pint-action from 2.3.1 to 2.4 Bumps aglipanci/laravel-pint-action from 2.3.1 to 2.4.

​

What’s Changed

• Fix Advanced Filters not querying when a column uses ->hidden() When a filament column uses ->hidden() the column appears in the Advanced Filter block picker, but does not filter nor show indicators. This is due to a bug with reorderableColumns that was rebuilding the table columns (in order to render them in the order the user desires), but mistakeningly excluding hidden columns. This in turns means that the column doesn’t exist in the table’s column for Filament to filter against. This PR fixes this.

​

What’s Changed

• Fix for UserViewResource when using RelationManagerConfiguration inside RelationGroups

​

What’s Changed

• fix has tenancy https://discord.com/channels/883083792112300104/1198735817137463357/1199 107950476804159

​

What’s Changed

• Allow setting the Badge Color on Favorites Bar button badges This PR should allow setting the Badge Color on Favorites Bar button badges
• Docs for badge color

​

New Contributors

• @abishekrsrikaanth made their first contribution

​

What’s Changed

• Bump dependabot/fetch-metadata from 1.6.0 to 2.0.0 Bumps dependabot/fetch-metadata from 1.6.0 to 2.0.0.
• Allow reorderable columns per resource
• Feature tooltips on preset views
• Add portuguese lang

​

What’s Changed

• Fix preset view visibility

​

What’s Changed

• lang: Update Dutch translation for consistency “Wereldwijd” is a direct translation of “Globally” (Worldwide), but it’s better to use the term “Globaal” for the Dutch language.
• Fix preset views interactions with table widgets

​

New Contributors

• @CodeWithDennis made their first contribution

​

What’s Changed

• Laravel 11 Support
• Translation updates
• Dutch translations

​

What’s Changed

• Update docs
• Fix user view resource filter with custom pages

​

What’s Changed

• Improve loading user and preset views from url When you mount (load) a page for the first time, if the plugin detects the activeUserView or activePresetView in the query string it will get that view including it’s toggled/reordered columns and load them. Now, all you need to do to load a User View or Preset View through a url is include the activePresetView or activeUserView id in the query string. For example: https://my-awesome-app.com/my-page?activeUserView=1 https://my-awesome-app.com/my-page?activePresetView=pending

​

What’s Changed

• Fix for or groups and removing active view when removing filters

​

What’s Changed

• Feature allow custom filter picker sorting By default (and currently) filters are sorted alphabetically. Now you can customize the filter picker sort order using ->filterPickerFilterSort(). Here’s how it works. 1. pass in false to sort the filters according to the way you have your table set up. This works independently of if you reorder columns in the UI as I don’t think the filter names should move around. So whatever order you have set up in your table would be the order in the filters. 2. pass in an array of column names and it will sort by those column names. You don’t have to set them all up. If you just want to make sure one it always first, you can just pass in that column’s name, and then all the rest of the columns will be added afterwards (in the same sort order as the table).

​

What’s Changed

• Fix non escaped labels

​

What’s Changed

• Fix failing tests with 3.2

​

What’s Changed

• Fix isRemovingAllFilters

​

What’s Changed

• Fix issue with using preset views without key names
• Fix issue with using preset views without key names

​

What’s Changed

• Fix SQL column injection vulnerability

​

What’s Changed

• Compatibility update with Filament v3.2 This PR adds compatibility for Filament’s new Apply Filter option.

​

What’s Changed

• Qualify column in Advanced Filter

​

What’s Changed

• Bump aglipanci/laravel-pint-action from 2.3.0 to 2.3.1 Bumps aglipanci/laravel-pint-action from 2.3.0 to 2.3.1.
• Add missing down method to migration
• Improve default preset views on initial load
• Dont show hidden table columns in reorderable columns
• Fix toggled and sorting columns UI bug
• Fix for view icons in table builder
• Improve advanced filter layout with long labels

​

What’s Changed

• Reset table search on default

​

What’s Changed

• Add hook for managed related resources
• Allow default view to be configured on resource

​

What’s Changed

• Fix filter indicator with simple string indicators

​

What’s Changed

• Add options for filter indicator labels

​

What’s Changed

• Refactor to cache methods
• Update README.md
• Allow label to be set on overriden filters

​

What’s Changed

• Update numeric filter to support scoped relationships

​

What’s Changed

• Add additional css selectors

​

What’s Changed

• Cache PresetViews

​

What’s Changed

• Fix filter builder “or” translation

​

What’s Changed

• Fix buildFilterIndicators method

​

What’s Changed

• Fix Filament theme css

​

What’s Changed

• Fix standalone tablebuilder guard

​

What’s Changed

• Only show indicator groups when or groups are enabled
• Update rtl css
• Allow custom auth guards

​

What’s Changed

• Fix resource widgets no appearing in user views resource
• Fix userview when no filters are present
• Add Laravel 10 requirement to docs

​

What’s Changed

• Expand multi-tenancy support
• Fix css end alignment on mobile
• Feature include, exclude, default operators

​

What’s Changed

• Implement aggregate relationship columns
• Prioritize options in selectFilter

​

What’s Changed

• Fix or groups

​

What’s Changed

• Improve TextFilter when using is and is_not with relationships
• Fix managedPresetViews with different user model
• Improve docs on defaultFilters

​

What’s Changed

• Allow disabling of “or” groups
• Fix down method migrations

​

What’s Changed

• Fix tenant migration when not on default panel

​

What’s Changed

• Improve Add Tenancy Command

​

What’s Changed

• Improve selectFilter with many to many relationships

​

What’s Changed

• [FIX] Improve default filter state

​

What’s Changed

• [Feature] support multi-tenancy

​

What’s Changed

• [Docs] add new is empty and is not empty operators
• [DOCS] Clarify Select Filter naming
• [DOCS] Update min version requirement
• Bump dependencies
• Update french translations for isEmpty and isNotEmpty
• Improve isEmpty and isNotEmpty queries

​

What’s Changed

• Fix missing variable

​

What’s Changed

• Fixes
• Add french translation to filter builder
• Add isEmpty and isNotEmpty to textFilter and selectFilter

​

What’s Changed

• Support modal, above, below filters layouts

​

What’s Changed

• Fix for RM with configuration When RM’s have a configuration like: php public static function getRelations(): array { return [ RelationManagers\CommentsRelationManager::make([ 'lazy' => false, ]), ]; } they get wrapped in a RelationManagerConfiguration object which in turn causes an error when accessing the UserViewResource.

​

What’s Changed

• Fix filter picker from flipping

​

What’s Changed

• Feature filter builder search and columns
• Arabic filter builder lang and fix

​

What’s Changed

• Support DB prefixes

​

What’s Changed

• Update filter indicators to new API

​

What’s Changed

• Update views for new core changes

​

What’s Changed

• Improve column filter api

​

What’s Changed

• Feature: column based query builder

​

What’s Changed

• Fix wrong config size

​

What’s Changed

• Update Advanced Filter for Filament’s new slideover/modal options

​

What’s Changed

• Allow resource navigation icon to be null

​

What’s Changed

• Fix when table used in layout mode

​

What’s Changed

• Update favorite bar spacing after core RM update Filament PR #8652 updated the RM spacing. This PR updates the favorites bar view accordingly.
• Docs update
• Fix getTableFilterDefaultState

​

What’s Changed

• Fix loading default preset view on first page load

​

What’s Changed

• Improve preset views when reloading

​

What’s Changed

• Fix column reordering with multiple relationships This PR fixes an issue with reordering when multipled relationships of the same type were being used (customer.name, customer.email). Filament stores toggledColumn data in an undotted array in the session. Usually this works fine, and the initial PR for reordering columns modified this array. However, when there are multiple relationships, this will group the relation columns together. This PR introduces an ordered array sidecar to handle this in both the database and the session. It also fixes an issue with default preset views, and makes the logic more robust.

​

What’s Changed

• Feature allow favorites bar to be disabled

​

What’s Changed

• Add Panel Page helper class and docs
• Fix reseting table column searches
• Add Arabic translation and fix RTL

​

What’s Changed

• Update actions
• feat(lang): add german translations
• feat: favorites bar theme enum This PR introduces an optional enum to the favoritesBarTheme() function. I had to first dig through the code, to find out that branded tabs are called tabs-brand and simple links are called links-simple. The enum provides more clarity and makes it easier for the user to select their desired theme. This introduces no breaking changes as the underlying strings where not changed.
• Fix persist column searches

​

What’s Changed

• Improve user view resources with multiple panels

​

What’s Changed

• fix: missing Closure import for PresetView concern
• Update README.md

​

New Contributors

• @Quadrubo made their first contribution

​

What’s Changed

• Allow expand view position to be configured

​

What’s Changed

• Refactor

​

What’s Changed

• Fix reorderable columns with relations

​

What’s Changed

• Fixes for advanced filters

​

What’s Changed

• Implement advanced filter builder

​

What’s Changed

• Fix error when removing columns

​

What’s Changed

• Bump stefanzweifel/git-auto-commit-action from 4 to 5 Bumps stefanzweifel/git-auto-commit-action from 4 to 5.
• Support multiple panels

​

What’s Changed

• Fix user views when no filters are present

​

What’s Changed

• Add quick save to table

​

What’s Changed

• Fix missing custom view classes

​

What’s Changed

• Fix storing toggle column order in db
• Feature replace user views

​

What’s Changed

• Fix non favorited global views not appearing in favorites bar on upgrade

​

What’s Changed

• Fix closure

​

What’s Changed

• Fix missing quick color property value

​

What’s Changed

• Add tips and tricks to docs
• Allow closure in plugin config

​

What’s Changed

• Update README.md

​

What’s Changed

• Update README.md

​

What’s Changed

• Update docs for upgrading migrations

​

What’s Changed

• Detach user managed views on delete

​

What’s Changed

• Update for newest Filament v3 alpha
• v3 updates
• Fix relation managers
• Fixes for v3
• Fix default method
• Update deprecated methods
• Fix hiding select create form
• Fix for new v3 color api
• Follow v3 tailwind and css recommendations
• Fix conflicting method names
• fix dev filter sets with relation managers
• Update from v1
• v3 service provider update
• Icon component updates
• Update README.md
• Update README.md
• Update README.md
• Docs update
• Update README.md
• Build
• Docs update
• Update README.md
• Update composer.json
• Update HasFavorites.php
• Update README.md
• v3 updates
• Favorites bar fixes
• Update IconSelect.php
• Icon update
• Update to new v3 render hooks
• Update translation and stubs for v3
• Bump dependabot/fetch-metadata from 1.5.1 to 1.6.0 Bumps dependabot/fetch-metadata from 1.5.1 to 1.6.0.
• fix filament forms affixes error
• Fluently instantiate
• v3 initial release
• Initial fixes
• Build css
• Update naming of example files
• Fix user view query
• User View Query fix and Quick Save name change
• Allow quick save icon to be configured
• Improve icon select with caching and excluding
• Implement view manager in table toolbar
• Improve favorite view sorting
• Readme updates
• Add convert icon helper
• Update README.md
• Update README.md
• Bump actions/checkout from 3 to 4 Bumps actions/checkout from 3 to 4.
• Fix resetting filter forms
• Bump toggle-icon dependency to stable

​

What’s Changed

• Update README.md
• Bump actions/checkout from 3 to 4 Bumps actions/checkout from 3 to 4.
• Fix resetting filter forms

​

What’s Changed

• Update README.md

​

What’s Changed

• Readme updates
• Add convert icon helper

​

What’s Changed

• Improve icon select with caching and excluding
• Implement view manager in table toolbar
• Improve favorite view sorting

​

What’s Changed

• Allow quick save icon to be configured

​

What’s Changed

• User View Query fix and Quick Save name change

​

What’s Changed

• Fix user view query

​

What’s Changed

• Update naming of example files

​

What’s Changed

• Build css

​

What’s Changed

• Initial fixes

​

What’s Changed

• Fluently instantiate
• v3 initial release