Closed (fixed)
Project:
Facets
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Nov 2016 at 15:20 UTC
Updated:
7 Aug 2017 at 09:25 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
divined commentedComment #3
borisson_I've just confirmed this - not sure how we should resolve it though. Not even sure if this is facets or search api related. I guess we'll need to discuss this.
In any case, we also need tests for this - our current language-specific tests are very basic.
Comment #4
borisson_Adding tag
Comment #5
divined commentedAdding Count limit processor solve half of problems.
But we have another:
3 Node, 2 Terms
Node1 with Term1
Node2 with Term1 and Term2
Node3 with Term2
--
Select facets for all Node titles and Term titles. Then unselect Node1, Term2 and then Node2.
All facet filter will disapeared from the page, and you get an empty result page.
Because you have active filter returns zero count only. (Active filters: Node3 and Term1)
---
I solve this problem in this variant:
New count limit processor:
Active results will skipped.
Comment #6
borisson_This is expected.
Facets use the same limitations as the query object passed, so when using views, add a filter to the view to limit to one language.
Otherwise, this is solved by adding a `hook_search_api_query_alter()` that limits the results to the current language.
I've added a test to make sure that this behavior works.
Comment #7
borisson_Needed a reroll
Comment #8
borisson_Comment #10
borisson_Committed and pushed.