Dynamic Facet Cascade provides a configurable block of AJAX-driven, dependent dropdowns (e.g., Make → Model → Version) that pre-filter a search results page built with Views on top of a Search API index. The module is heavily tied to Views: presets can only target Views page displays whose base table is a Search API index, and the facets it pre-fills must use that display as their facet source (search_api:views_page__{view}__{display}). Site builders define reusable "preset" config entities mapping each dropdown level to an existing facet; the module derives the backing vocabularies and term-reference fields at runtime — no hardcoded field names. Presets support multiple tabs, each driven by a "dominant" dimension (e.g., By Year / By Type), with optional locked or hidden pre-selected terms. On submit, the user is redirected to the Views page with standard Facets query parameters (f[0]=facet:tid), so results render with the facet widgets already active. An optional content-based mode restricts dropdown options to combinations that actually exist in the same Search API index the view is built on.
How it differs from similar projects:
Facets renders widgets on the search view to refine existing results; this module provides a pre-filter form that can be placed anywhere (e.g., the front page) and hands off to the Views/Facets page.
Hierarchical taxonomy widgets (e.g., Facets Hierarchy processor, Hierarchical Term Formatter, Cascading Select / cshs) operate on a single hierarchical vocabulary or a single entity-reference field. This module cascades across separate flat vocabularies linked by term-to-term entity reference fields, discovered dynamically from field config.
Comments
Comment #2
vishal.kadamComment #3
avpadernoThank you for applying!
Before giving links helpful to understand how the review process works, what to expect from a review, and what to do to avoid a review takes more time than needed, I would like to thank all the reviewers for the work they do.
These applications are volunters-driven, which also means it is not possible to predict when an application will be marked fixed and the applicant will get the permission to opt projects into security advisory policy. While we aim to make an application as quick as possible, it is also important for us that more people review the project used for an application. In this way, we make sure applications do not miss some important points that should be instead reported.
Applications are not meant to be complete debugging sessions that eliminate every existing bug, though. I apologize if sometimes applications seem to go into too-detailed reviews.
Please read Review process for security advisory coverage: What to expect for more details and Security advisory coverage application checklist to understand what reviewers look for. Tips for ensuring a smooth review gives some hints for a smoother review.
The important notes are the following.
Keep in mind that once the project is opted into security advisory coverage, only Security Team members may change coverage.
To the reviewers
Please read How to review security advisory coverage applications, Application workflow, What to cover in an application review, and Tools to use for reviews.
The important notes are the following.
For new reviewers, I would also suggest to first read In which way the issue queue for coverage applications is different from other project queues.
Comment #4
vishal.kadam1. FILE: src/Entity/DynamicFacetCascadePreset.php, src/Plugin/Block/DynamicFacetCascadeBlock.php
Projects that are compatible with Drupal 10 or higher versions should use attributes instead of annotations. This means requiring at least Drupal 10.3, but this is not an issue, considering which Drupal core versions are nowadays supported.
2. FILE: src/Form/DynamicFacetCascadeForm.php
FILE: src/Plugin/Block/DynamicFacetCascadeBlock.php
FILE: src/Plugin/Deriver/DynamicFacetCascadeBlockDeriver.php
Modules which are compatible with Drupal 10 and higher versions are expected to use constructor property promotion.
Comment #5
vishal.kadamI am changing priority as per Issue priorities.