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.
Comment | File | Size | Author |
---|---|---|---|
#5 | Views_caching_ui.png | 29.72 KB | bisonbleu |
Comments
Comment #2
mikemadison CreditAttribution: mikemadison at Pacific Northwest National Laboratory commentedComment #3
mikemadison CreditAttribution: mikemadison at Pacific Northwest National Laboratory commentedComment #4
mikemadison CreditAttribution: mikemadison at Pacific Northwest National Laboratory commentedAs far as I can tell, updating to the most current dev versions of search api, search api solr, and facet api resolved this issue.
Comment #5
bisonbleu CreditAttribution: bisonbleu commentedI 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.
Works for me.