Open trackleft opened 4 months ago
After enabling and configuring the View Reference Filters module on a multidev site, I successfully ran several tests (see screenshots below).
Note: The module appears to function correctly; however, it is not yet covered by the security advisory policy. There is an open ticket to include it in the security advisory policy.
Also, I reached out to the module maintainer, @roborew, via Slack and the ticket, but haven't received a response yet.
Content type: Expose filter option
Views Paragraphs: Checkbox for enabling and disabling the exposed filter.
After enabling the exposed filter
View with the exposed filter disabled
Troy mentioned we should keep the argument filters Dana asked how to set the operator
TODO: add back optional views to config.
Questions:
TODO remove the option to expose the filter.
- should we have both "Select a Category" and "Argument" options?
My opinion is that the goal should be to replace the existing "Argument" option with the "select a category" option.
- if Category and Argument do not reference same Taxonomy, no items shown
This will cause a lot of trouble for us.
- What views would we add this to?
Hopefully all of the views that are currently configurable with the argument.
- If we add to existing views, argument would remain after upgrade so View is not changed, but we then run into the issue of clients needing to be educated on the fact that there are two different settings that change the same thing in Views?
Hopefully we can write a migration/database update to move existing values for the argument into new values for select a category option.
Description
Related issues
Closes #3443
How to test
Types of changes
Arizona Quickstart (install profile, custom modules, custom theme)
Drupal core
Drupal contrib projects
Checklist