I recall this being an issue a year or two back, but I didn't think it was still an issue. This could be an issue in configuration (or it could be a bug in module...)

I have a view that is configured to use a content index. I have tried caching it with the search specific cache option, both with the rendering cached and not (always with the results cached). The result is that on the first page load, the facets load. When I do a facet selection, or I reload the page, the facets vanish from the page (and by vanish, I mean the entire block is gone). Clearing the caches causes the block to reappear, and then on the next reload it's gone again.

I have done some digging and I've found a lot of older issues amongst both the Search API and Facet API issue queues, but nothing terribly recent. Am I missing something here?

There are no errors in the logs.

The facets work perfectly fine with the view when caching is disabled.

The behavior is occurring for the system admin account and for anon users.

CommentFileSizeAuthor
#5 Views_caching_ui.png29.72 KBbisonbleu
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mikemadison created an issue. See original summary.

mikemadison’s picture

Title: Cached View + Facet API Causing Issues » Cached Search API View Causes Facet Blocks to Vanish
Issue summary: View changes
mikemadison’s picture

Status: Active » Closed (works as designed)

As far as I can tell, updating to the most current dev versions of search api, search api solr, and facet api resolved this issue.

bisonbleu’s picture

FileSize
29.72 KB

I just ran into this issue. But it was because I used the standard Time-based caching option instead of the Search API specific Search-specific option.

Views_caching_ui

Works for me.

  • search_api-7.x-1.20+20-dev
  • facetapi-7.x-1.5
  • drupal-7.54