It can be desirable for autocomplete results to use a different operator to that used for regular views results.

An example use case for this is if you were searching for articles from newspaper two of which were "The Sun" and "The Sun on Sunday". If the filter operator is set to "Contains" then typing "Sun" into the exposed filter will display both results, however when clicking on "The Sun" both results will also appear in the view, which is not ideal. If the filter operator is set to "Is equal to" then typing "Sun" into the exposed filter will display no results, which pretty much renders autocomplete useless. However if the autocomplete operator is set to "Contains" and the regular views operator is set to "Is equal to" then typing "Sun" into the exposed filter will display both results, and after clicking on "The Sun" then the view will only show results for "The Sun", perfect!

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

MustangGB created an issue. See original summary.

MustangGB’s picture

Assigned: MustangGB » Unassigned
Status: Active » Needs review
FileSize
4.86 KB

Here's a patch, I've tested it using the string handler, but not the combine handler.