- Issue created by @akalam
- Merge request !204Issue #3444352: Views exposed form is not reflecting the active facets when... → (Open) created by akalam
- Status changed to Needs review
11 months ago 12:34pm 30 April 2024 - 🇪🇸Spain akalam
Created a MR implementing a fix using a form alter. I had to enable the static_caching on the facets config entity to ensure the active facet values are still available when loading the facet on a later phase (in our case the form alter). The general activation of static caching of config_entities is being discussed here #1885830: Enable static caching for config entities →
- 🇪🇸Spain tuwebo
Hello,
There have been some changes lately for 3.0.x-dev, and looking into this issue (and commit) #3485860-11: TypeError: array_values(): Argument #1 ($array) must be of type array, null given → I wonder if anyone can confirm if this patch is still necessary or not (I can't test it properly right now). Although the mentioned issue does not seem to be related, the code in the commit might be. - 🇪🇸Spain akalam
@tuwebo the MR is not applying neither a valid approach in the latest release 3.0.0 because of a big refactor, now the facets are direct filters on the view without using a separated facet config entity.
To the problems described in this issue is the fact that with facets as exposed filters the pre_query processors are not being applied.
Here's a new MR trying to solve the issue with the new approach. - Merge request !298Issue #3444352: Views exposed form is not reflecting the active facets when... → (Open) created by akalam