If you use apache_solr, you might also use apachesolr autocomplete
http://drupal.org/project/apachesolr_autocomplete

But custom_search blocks do not show the autocomplete.

This patch fixes that.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

jdanthinne’s picture

The 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?

askibinski’s picture

yes, the default core search already works with apachesolr_autocomplete.

jdanthinne’s picture

Component: Code » Blocks submodule
Status: Needs review » Fixed

Ok, committed to DEV.
Thanks.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

fourmi4x’s picture

Version: 6.x-1.4 » 6.x-1.x-dev
Category: feature » support
Status: Closed (fixed) » Active

I 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

jdanthinne’s picture

Status: Active » Needs review
FileSize
1.32 KB

Please 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!

fourmi4x’s picture

Thank 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)

jdanthinne’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.