Closed (fixed)
Project:
Search API
Version:
7.x-1.17
Component:
Plugins
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 Apr 2016 at 22:06 UTC
Updated:
19 May 2016 at 11:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
maxcpr commentedComment #3
heykarthikwithuComment #4
drunken monkeyThanks for reporting this problem!
Your proposed solution isn't quite right, though, or not far-reaching enough. The problem is that, for some reason, in #2450227: Ignore parent terms in facets when operator is OR we seem to have forgotten that this query type is used not only for taxonomy terms, but for nearly all values (except dates).
Your solution has some invalid code, but most of all won't fix the underlying problem we tried to solve in the other issue for hierarchical fields that are not taxonomy terms. The proper solution is to check that a hierarchy call is present (as it will be for taxonomy terms) and then use that instead of
taxonomy_get_parents_all().Please see the attached patch, and verify that it, too, solves your problem!
PS: It seems you (like many others – it's really easy to misinterpret) are confused by the "Issue tags" field. As the guidelines state, they aren't meant for free text tags related to the issue, but only for specific categorization purposes, usually by module maintainers.
So, if you aren't sure your current usage is correct, please just leave the field empty.
Comment #5
maxcpr commentedThanks for this patch! It seems that it works. At least not not worse than mine :)
I do not need the hierarchy in queries - so may be I didn't try to dig into it rather deep..
Hope this patch will be included in future updates!
Comment #7
drunken monkeyGood to hear it works, thanks for testing!
Committed.
Comment #8
drunken monkey