-
Notifications
You must be signed in to change notification settings - Fork 7
Open
Description
Currently, the All filter option is hard-coded to always be included. It would be nice if there were an option to enable/ disable this option for collection filters. This should be usable with all of the input_type
options.
Issues
How should the filter behave if we remove the all option?
-
Default to what would be the first filter option
- Less user configuration
- How can we filter when visiting the page without any url queries? The current traversal event subscriber doesn't seem to trigger the filtering if we don't have
collectionfilter=1
as a query parameter,meaning it isn't possible to filter the results. We could lookup the portlet and check if it needs filtering, but this will get really expensive if we're doing it every traversal.
-
Provide an option to define what the default
- We would have to check the catalog for all the available options when setting up the portlet
- We still wouldn't be able to filter without the event subscriber triggering for the initial page visit
Metadata
Metadata
Assignees
Labels
No labels