Closed (fixed)
Project:
Search API
Version:
7.x-1.x-dev
Component:
Facets
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
27 Feb 2012 at 11:18 UTC
Updated:
2 Oct 2012 at 08:31 UTC
Jump to comment: Most recent file
Comments
Comment #1
drunken monkeySeems like you have already fixed this yourself, or implemented a work-around. If the former, please share! If the latter, please see whether you can reproduce the bug with some minimal setup locally and reply.
Comment #2
attiks commentedI'm having a similar problem
Comment #3
attiks commentedIt gives to right count if you configure the facet to unlimited, reason is that the count code only works on the returned facet items, while it should work on all facet items (query_type_date.inc)
Comment #4
attiks commentedIt works for node create/changed date, but not for other date fields.
Comment #5
egarias commentedI had this problem with date created.
Following recomendations I try to set "unlimited"
configure facet display>global options>hard limit
this shows the error:
on my view:
Any help?
Thanks!
Comment #6
attiks commentedThat error is coming from elsewhere (i think facetapi), search the source for "-1" and change it to "99999999"
Comment #7
egarias commentedFollowing your recomendation I added a new option in
facetapi.admin.inc
line 556
$hard_limit_options = drupal_map_assoc(array(3, 5, 10, 15, 20, 30, 40, 50, 75, 100,999999));
and it works!
Comment #8
attiks commentedNew issue created for unlilmited, see #1626910: Unlimited not working with search_api and search_api_db
Original problem still the same:
Comment #9
drunken monkeyThe error in #5 should be fixed with #1550772: Facet hard limit set to "no limit" causes SQL error. Please try the latest dev version! No need to hack any modules. ;)
Regarding the original problem: you're right, date facets won't really work unless there is no hard limit. Using "unlimited" will be extremely slow, though, for large result sets, so there's some caution necessary there. I hope I alleviated this by also adding a warning to the description of date facets. In any case, they'll now always use no limit for their facet queries.
Please help test the attached patch!
Comment #10
drunken monkeyHum. It seems I already committed this.