Autocomplete for Views exposed filter ignores configured fields [#2773659]

I am using Search autocomplete with an exposed filter from Views. For autocomplete, I want to restrict the search to just the title field even though the actual search uses more fields than that.

It seems that all fields configured (in Views) for the exposed filter are searched. It does not matter what configuration I use on admin/config/search/search_api/index/*/autocomplete/search_api_views_*/edit: I can select a different "Views display" or I can select different fields in "Override used fields" but these settings seem to be ignored.

Am I doing something wrong or is this a bug?

Looking at the code from search_api_autocomplete_form_views_exposed_form_alter() I do not see that the configuration is being used anywhere. I suppose I can use hook_search_api_autocomplete_views_fulltext_fields_alter() to fix this. Is that what I am supposed to do?

Tested with 7.x-1.4 and 7.x-dev.

Comments

Comment #1

27 July 2016 at 18:44

benjifisher created an issue. See original summary.

Comment #2

benjifisher

he/him or they/them

English

Boston area

CreditAttribution: benjifisher commented 27 July 2016 at 19:30

In case someone else finds it useful, here is the code I used:

/**
 * Implements hook_search_api_autocomplete_views_fulltext_fields_alter().
 *
 * Get Search API autocomplete to respect settings when used with an exposed
 * filter from Views.
 *
 * @see https://www.drupal.org/node/2773659
 */
function mymodule_search_api_autocomplete_views_fulltext_fields_alter(array &$fields, SearchApiAutocompleteSearch $search, view $view) {
  if (!empty($search->options['suggester_configuration']['fields'])) {
    $view->filter['search_api_views_fulltext']->options['fields']
      = $search->options['suggester_configuration']['fields'];
  }
}

Comment #3

drunken monkey

he/him

German

Vienna, Austria

CreditAttribution: drunken monkey as a volunteer commented 22 August 2016 at 16:11

If you look at the beginning of search_api_autocomplete_autocomplete() (around line 30), you'll see that as long as fields are set in the autocomplete options, those passed from somewhere else will be completely ignored.

However, are you maybe using an older (more than a year) version of the "Database search" module? See #2483123: Narrowing autocomplete suggestions to one field – we had the problem there that the fields were completely ignored.

Comment #4

iamweird CreditAttribution: iamweird commented 1 September 2017 at 12:19

Component:

Code

» General code

Yes, but it's $search->options['suggester_configuration']['fields'], not $search->options['fields'] for me (I've got 7.x-1.5).

Comment #5

marinex CreditAttribution: marinex commented 24 June 2019 at 21:32

Hi I have same issue:
search_api_db 1.7
search_api_autocomplete 1.6

~~It does not respect settings on a field in the views~~
fix.:My issue is related to the getAutocompleteSuggestions

After some digging I notice that code below override views field options:
File: SearchApiAutocompleteServerSuggester.php

  public function getAutocompleteSuggestions(SearchApiQueryInterface $query, $incomplete_key, $user_input) {
    if ($this->configuration['fields']) {
      $query->fields($this->configuration['fields']); // <----override field option because fields are set in the search_api_autocomplete_autocomplete - file:search_api_autocomplete.pages.inc
    }
    return $query->getIndex()->server()->getAutocompleteSuggestions($query, $this->getSearch(), $incomplete_key, $user_input);
  }

~~It is needed to fix!~~

After setting of configuration on administration all works as designed! Sorry!