Closed (duplicate)
Project:
Facet API
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
8 Feb 2012 at 16:45 UTC
Updated:
21 Apr 2016 at 14:10 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
osopolarFIX: check with empty().
Comment #2
cpliakas commentedThanks for the patch. The fix looks good, but ideally we shouldn't have to even call empty() since it is roughly 20% slower that just passing the value to if(). This is splitting hairs, but if we could avoid it that would be my preference. I'd rather make sure $this->dependenciesPassed[$facet['name']] is set for all facets.
Thanks for discovering the bug,
Chris
Comment #3
cpliakas commentedSo looking at this further, $this->dependenciesPassed[$facet['name']] is set for all active facets, meaning that an inactive facet is being processed for some reason. To me that is a bigger issue, so I need some more information to continue working on this.
Comment #4
osopolarYes you are right, it is a bigger issue and patch 1 seems not to be necessary. I use the facet blocks in a Panel page together with a search_api view to search. The blocks are on the left and the view is on the right side, therefore the blocks get rendered before the view. I guess this is the problem. I need to render the facet blocks first. For a workaround see: #1018420: Allow the possibility to control the order in which content is rendered #15.
Comment #5
cpliakas commentedThanks for debugging and reporting back. Based on this information, I am going to close as a duplicate of #1417456: Facets on non-search Search API pages broken by facetapi_block_list_alter removing the block since this seems to be related to the underlying cause.
Thanks,
Chris
Comment #6
kenorb commented