Default display of view cannot be used as a facet source

Created on 2 August 2023, over 1 year ago

This is perhaps for a very good reason, but it is causing me problems so I figure I have to flag it up!

I am using the TVI (Taxonomy Views Integrator) module to allow the use of a view per-term/vocabulary to override the default taxonomy page. The view I am using for this is a Solr-based search. Given that the Taxonomy module continues to handle the paths, it seems logical to create the view with only a Default display.

However, facets cannot be created using a view's Default display as the source - I have had to bodge things for now by using a Page display, which creates the secondary problem of a having to create a URL for that display which I don't want/need. I also tried an Embed display, which does allow facet creation, but doesn't seem to play ball with TVI.

Can anyone tell me whether it is by design that Default displays can't be used as facet sources?

💬 Support request

Status

Active

Version

2.0

Component

User interface

Created by

🇫🇷France paulbeaney

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @paulbeaney
Comment 7 days ago →
🇺🇸United States DamienMcKenna NH, USA
I'm running into a similar issue where I'm using the "page" display via TVI and the facets aren't being displayed though the block plugin is supposed to show.
Comment 7 days ago →
🇺🇸United States DamienMcKenna NH, USA
I think SearchApiDisplay::isRenderedInCurrentRequest() needs to be extended to check if the configured view is displayed on the current page.
Comment 7 days ago →
🇺🇸United States DamienMcKenna NH, USA
A prototype that checks if the current path is managed using TVI, then compares the current facet's Search API display against TVI's display.
@damienmckenna opened merge request.
Comment 7 days ago →
🇺🇸United States DamienMcKenna NH, USA

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024