Closed (fixed)
Project:
Custom Search
Version:
6.x-1.x-dev
Component:
Blocks submodule
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
18 Nov 2010 at 16:41 UTC
Updated:
5 Apr 2011 at 18:01 UTC
Jump to comment: Most recent file
Comments
Comment #1
jdanthinne commentedThe patch only applies the behaviour for the custom search blocks, and not the default theme/core search.
Is it what you intended to do, dear neighbour?
Comment #2
askibinski commentedyes, the default core search already works with apachesolr_autocomplete.
Comment #3
jdanthinne commentedOk, committed to DEV.
Thanks.
Comment #5
fourmi4x commentedI can't get this to work, I just have an input box without autocomplete in my custom search blocks.
However, in my default "Search form" block, I get 2 input boxes... ?!
- one with autocomplete => doesn't work : redirects to empty solr search
- one without autocomplete, preceded by "Containing any of the words: " => works fine
Is it normal to have 2 input boxes ?
Is there some special configuration to do to have the autocomplete in custom search block ?
NB :
- I'm using the latest dev of Apache Solr Search Integration, Apache Solr Autocomplete and Custom search
- I tested this both with"Drupal core autocomplete widget" and "Custom autocomplete widget" in Solr settings
Comment #6
jdanthinne commentedPlease try and this patch (or DEV version from tomorrow).
It enables the autocomplete function for the custom blocks.
But I don't have 2 input boxes in the default search block!
Comment #7
fourmi4x commentedThank you jdanthinne, the patch works perfectly!
(I still have my 2 input boxes in the default search block (weird!), but it's not a problem I will use custom blocks instead)
Comment #8
jdanthinne commented