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?

CommentFileSizeAuthor
#4 facets-n3378700-4.patch2 KBdamienmckenna

Issue fork facets-3378700

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

paulbeaney created an issue. See original summary.

damienmckenna’s picture

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.

damienmckenna’s picture

Title: Default display of view cannot be used as a facet source » Integration with TVI
Version: 2.0.6 » 3.0.x-dev
Assigned: Unassigned » damienmckenna
Category: Support request » Feature request

I think SearchApiDisplay::isRenderedInCurrentRequest() needs to be extended to check if the configured view is displayed on the current page.

damienmckenna’s picture

Status: Active » Needs review
StatusFileSize
new2 KB

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’s picture

Assigned: damienmckenna » Unassigned