Entity Reference Facet Link is an amazing module that detects facets that are applicable to entity reference fields and lets you choose one to be the link for referenced entities, so for example instead of getting a taxonomy term listing page you get a Faceted search view filtered to that term.
But it is looking at the old-style standalone facets only now.
#3527158: ERFL is incompatible with Facets Exposed Filters
I am not spotting anything on recommended shifts from facets that are there "own thing" versus those that ace at exposed filter on views in the documentation, release notes, nor (first time i saw they are a thing for modules!) change records.
And would Entity Reference Facet Link have to look at both at once, or are standalone facets deprecated enough that there could be a new version only looking at the Views exposed filters?
Comments
Comment #2
strykaizerFacets are now not a special usecase anymore, and are just a views exposed filter as any other views exposed filter.
This has the advantage that every solution works for all exposed filters, not only facets (e.g. views_filters_summary, better_exposed_filters, url handling thus ajax working, ...)
Since Entity Reference Facet Link uses the old system, that wont work anymore indeed.
There might be solutions which already fix this for all exposed filters, which should also work for facets (see entity_ref_filtering_link)
If not, let me know what is missing, so I might be able to help creating it.
I'm not a fan of supporting facet-specific modules anymore which shouldn't be facet-specific.
If we can write them more agnostic, it benefits all usecases.
Comment #3
strykaizer