-
Notifications
You must be signed in to change notification settings - Fork 904
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Select2 Filter Does Not Trigger a Change #5054
Comments
Hello there! Thanks for opening your first issue on this repo! Just a heads-up: Here at Backpack we use Github Issues only for tracking bugs. Talk about new features is also acceptable. This helps a lot in keeping our focus on improving Backpack. If you issue is not a bug/feature, please help us out by closing the issue yourself and posting in the appropriate medium (see below). If you're not sure where it fits, it's ok, a community member will probably reply to help you with that. Backpack communication channels:
Please keep in mind Backpack offers no official / paid support. Whatever help you receive here, on Gitter, Slack or Stackoverflow is thanks to our awesome awesome community members, who give up some of their time to help their peers. If you want to join our community, just start pitching in. We take pride in being a welcoming bunch. Thank you! -- |
I don't think it really matters, but I was trying to look for this in my email until I realized I used my work email address instead of my personal email 😄 |
Hi @rbzachary! I'm opening a PR to fix that issue https://github.com/Laravel-Backpack/PRO/pull/152 👌 Thank you for your report. |
Bug report
What I did
Unselected select2 filter
What I expected to happen
The selection clears out and triggers a change
What happened
It doesn't
What I've already tried to fix it
In the select2 filter, there is a line
$('#filter_'+filterKey).val(null)
that I changed to$('#filter_'+filterKey).val(null).trigger('change');
Is it a bug in the latest version of Backpack?
After I run
composer update backpack/crud
the bug... is it still there? Backpack Pro, yesBackpack, Laravel, PHP, DB version
When I run
php artisan backpack:version
the output is:The text was updated successfully, but these errors were encountered: