- Issue created by @rauch
- 🇨🇦Canada phjou Vancouver 🇨🇦 🇪🇺
This module was supposed to stay quite simple like the Search Block from Core. So I am not sure if this module should include an advanced feature like this.
But you probably can use this module to achieve it:
https://www.drupal.org/project/views_exposed_filter_blocks → - 🇩🇪Germany rauch
The module cannot be used if you want to offer more filters on the search page apart from the text search. For example, filters by category or content type. These filters would then also be in the block in which you only want to have the text search.
- 🇬🇧United Kingdom SirClickALot Somerset
@phjou → ,
I've got to say that I disagree with on your first point. This module is extremely useful for exposing the Search API and does so perfectly in my view except that the
search_api_autocomplete
does not kick in automatically.Given the description of what this module 'does' — takes the search view search box and shoves it in a block — I don't really understand why?
In our opinion and use-case, the auto-complete feature is crucial to UX because if it 'spots, and highlights just the right candidate' then the user does no even need to hit Enter to do the search and that is really valuable.
So I suppose question is one of: area you saying that you don't think it should work and that you cannot easily enable to work?
Thank you