-
Notifications
You must be signed in to change notification settings - Fork 50
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
Collections search fix #1717
base: Development
Are you sure you want to change the base?
Collections search fix #1717
Conversation
If this fixes the following issue, it might be best for this fix to be pushed as a Hotfix. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to work exactly as expected. I kicked the tires around my local machine, looking for reversions (why would I have included '#search-form-colls input[name="cat[]"]:checked'
??), and couldn't find any.
On the github issue, Ed mentions that there's still a stlying fix that would need to accompany this (see #1703 (comment)).
Could I trouble you to implement the js fix as well?
I believe I fixed this. Also fixed the map search issue when deselecting category wouldn't deselect "Select/Deselect all collections" checkbox. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems to be working great!
Changes Made:
removed line that adds category value to collections list which created an issue when category value is the same as some collection's value giving the wrong result.
Pull Request Checklist:
Pre-Approval
master
branch and squash and merged back into themaster
branch.Development
branch, NOTmaster
[3.1] Excluding collections from search results is not working #1703
Post-Approval
Development
branch, remember to use the squash & merge optionDevelopment
branch into the master branch, remember to use the merge optionmaster
branch, a subsequent PR frommaster
intoDevelopment
should be made merge option (i.e., no squash).Development
branch before a tagged release (i.e., before an imminent merge into the master branch), make sure to notify the team and lock theDevelopment
branch to prevent accidental merges while QA takes place. Follow the release protocol here.Thanks for contributing and keeping it clean!