Facets 3.x - Exposed filters roadmap

If the filters are moved to "Exposed form in block" they don't get updated (removed / count changed) as they are applied. (Filter works, updating of the filters does not.) With "Exposed form in block: No" the facets work and update themselves flawlessly.

"Facets 3 will not support AJAX when using Facet blocks."

This seems like kinda a broken model. Facets usually lives in a separate location on the page from exposed filters like the search text. So merging them like this seems like it breaks the most common use case for using facets.

+1. I agree with neclimdul

@neclimdul We are aware of that limitation.

For now we focus on 100% working ajax support with exposed filters OR blocks without ajax.
So you still can use blocks, there just wont be any ajax support on those.

Once the roadmap above is completed, we will look into a solution to split exposed filters in multiple blocks, so you will have best of both worlds. Mkalkbrenner already has a working solution, but it will require some work before it can be published.

@mlncn
As discussed on slack, it looks like this is a core issue. A patch already exists, see
https://www.drupal.org/project/drupal/issues/3090504 🐛 Views - update filters block on ajax request Needs work

@neclimdul @trickfun

You are able to place your facets (or any other filter/exposed sort, pager) etc. using configurable_views_filter_block
I updated the text above to document this.

Just FYI was testing out the dev branch and now noticed facets don't appear as view filters like it did in beta1.

Scratch that, see it needs an additional module now.

BTW with new views exposed facet how come no soft limit?

@smustgrave
Widget rendering is handled by Better Exposed Filters.
So if you want soft limit (which is client side), you'll need to contribute this feature to BEF.

Shouldn't be that hard, I'll add it to the todos above.

Automatically closed - issue fixed for 2 weeks with no activity.