- Issue created by @catch
- 🇦🇺Australia pameeela
Finally had a chance to look at this and I think the best course of action is to remove autocomplete from search for now. The calculation for me is that the autocomplete suggesting individual pages is not providing that much value, and it's causing a huge performance hit.
If we can make it work without changing the performance I think it's a nice addition. But making it a separate recipe does not really solve the problem in my opinion. I still don't think it would be worth the performance hit of adding it. So if we can fix the performance, we can include it by default again. (Although, as noted in 🐛 Search broken without search_api_autocomplete Active , there would be work to ensure that it still could be turned off if needed.)
- First commit to issue fork.
- Merge request !499Issue #3501076: Remove search_api_autocomplete until performance can be improved → (Open) created by annmarysruthy
- 🇮🇳India annmarysruthy
Removed autocomplete in MR !499. Kindly review. however even if we enter text in searchbox, relevant results are not displayed. This is already mentioned in https://www.drupal.org/project/drupal_cms/issues/3501069 🐛 Search broken without search_api_autocomplete Active
- 🇬🇧United Kingdom catch
This will need additional changes to drupal_cms_olivero per 🐛 Search broken without search_api_autocomplete Active . I think that could be included here if we're removing the whole feature - e.g. take any autocomplete-specific theming out of drupal_cms_olivero.
Making it work both with and without autocomplete could happen if/when autocomplete is added back and we could repurpose the other issue for that.
- 🇦🇺Australia pameeela
Making it work both with and without autocomplete could happen if/when autocomplete is added back and we could repurpose the other issue for that.
Agreed that's separate, for now we just need to make it work without autocomplete.
