- Issue created by @akalam
- 🇳🇿New Zealand quietone
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
- 🇧🇪Belgium StryKaizer Belgium
Hi,
Can you confirm that you are using "facets exposed filters", and that your facets are placed in the Views UI, as exposed filters?
It looks like you are still using the old "facets as block" method, which is not supported for this usecase.You can find more info on how to use the new Facets 3 workflow overhere: https://project.pages.drupalcode.org/facets/exposed_filters/
- 🇳🇱Netherlands Lendude Amsterdam
Moving to PMNMI to see if this occurs in a scenario that is supported.
- 🇪🇸Spain akalam
Yes, I'm using facets as exposed filters with the latest approach. The facets source entity is configured as "query string" url processor, the facet entities have been removed, and the facets are added to the view as exposed filters. Then, I'm setting the exposed filter form as a separated block so I have 2 blocks, one for the view exposed filters and another block for the view results. By last, I've placed both blocks on layout builder
- Merge request !12005Issue #3518730: Facets v3 not visible in Layout Builder with Views exposed filters until AJAX search → (Open) created by akalam
- 🇪🇸Spain akalam
I've created a MR executing the view in the viewExposedFormBlocks() method, instead of initializing the handlers. views has a protection mechanism to ensure the view won't get executed twice, so there shouldn't be an impact on the performance caused by this change
- 🇺🇸United States smustgrave
Not sure how but feel we will need a test to show how this is broken in core and not in contrib.
- 🇺🇸United States smustgrave
Still feel we need some kind of test coverage that shows why this change is needed, but do apologize not sure what that test would look like.
- 🇮🇳India manishsaharan New Delhi
Same issue is available in Drupal 10.5.2 as well and the above fixes works for the same.