Updating to Search API 7.19 (from 7.18) and Sarnia facets no longer show up on the page [#2768773]

We have a panel page showing a view and facets from a Sarnia Solr data set.
When we updated to search_api V1.19 (from search_api V1.18) the facets no longer displayed on the panel page.
Normally when this happens you would see the "broken/missing" info on your facet titles in the panels admin page for 'content', but in this case they looked correct.
Adding known facet selection(s) parameters on the URL filtered the data even though the facets themselves didn't display.
The facets don't show, but the view showing the filtered data does show, and the filtered/faceted data displays correctly - even if the facets don't display.
The facets show as being able to be placed on a panel page in the Panels admin when clicking the cog wheel for panels "Add Content" then selecting "facet api" from modal and picking the facet you need. It just never displays on the panel page, but shows as being placed in the Panels variant "Content".

Backing out the search_api V1.19 changes restored the facets displaying. (So reverting back to search_api V1.18)

Comment	File	Size	Author
#2	use-new-facet-key.patch	1017 bytes	jmdeleon
#2	7.x-1.x: PHP 5.5 & MySQL 5.5, D7 CI error
	Screen Shot 2016-07-18 at 1.45.28 PM.png	92.11 KB	mr_scumbag

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

18 July 2016 at 18:29

mr_scumbag created an issue. See original summary.

Comment #2

jmdeleon CreditAttribution: jmdeleon commented 18 July 2016 at 19:40

File	Size
use-new-facet-key.patch	1017 bytes
7.x-1.x: PHP 5.5 & MySQL 5.5, D7 CI error

Turns out a similar fix to the general Search API Facet API term plugin, as described in this general Search API issue #2700011: Multiple Indexes and Facets Interacting with Each Other, needed to be applied to the Sarnia Facet API sarnia_term plugin...

I am attaching a patch here that implements the same fix in the Sarnia Facet API plugin.

Comment #3

jmdeleon CreditAttribution: jmdeleon commented 19 July 2016 at 14:22

Status:

Active

» Needs review

Comment #4

19 July 2016 at 14:35

Status:

Needs review

» Needs work

The last submitted patch, 2: use-new-facet-key.patch, failed testing.

Comment #5

ben.kyriakou CreditAttribution: ben.kyriakou at Cogapp commented 20 July 2016 at 11:06

I gave this patch a go and it didn't seem to fix the issue for me using Search API 7.x-1.19, so I've likewise backed off to 1.18 for now.

Comment #6

21 July 2016 at 02:21

jmdeleon committed a9dfa8c on 7.x-1.x

Issue #2768773 by jmdeleon, mr_scumbag: Updating to Search API 7.19 (...

Comment #7

jmdeleon CreditAttribution: jmdeleon commented 21 July 2016 at 02:28

I committed this patch, as I had been having the same issues described originally without initially realizing it, and the fix applied did work for me with Search API 7.x-1.19 installed. I'd need more information on specific use-cases to keep tracking this down.

Comment #8

jmdeleon CreditAttribution: jmdeleon commented 28 July 2016 at 14:13

Tangentially related to this issue: If you are using the Facet API Current Search module with Sarnia indexes and Features, the following patch to the Current Search module may be useful: #1469002-27: Current search block's searcher display settings not exported