Search API Support

Created on 31 January 2019, almost 6 years ago
Updated 23 August 2024, 4 months ago

The shs module is currently not compatible with search_api. The attached patch should provide it.

Feature request
Status

RTBC

Version

2.0

Component

Code

Created by

🇺🇸United States jienckebd

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇵🇹Portugal nsalves

    It seems the merge request was not yet approved so here's the patch rerolled for the rc3 release

  • 🇳🇬Nigeria chike Nigeria

    Using Drupal 10, patch #12 gives me duplicate filters when viewed as admin, one with SHS and the other a regular dropdown. Viewing as anonymous one only sees the regular dropdown and doesn't see the one with SHS.

  • 🇳🇬Nigeria chike Nigeria

    The issue I reported at #13 is not related to patch #12. I removed the patch and added a filter on a regular view (not using Search API) and the issue persisted. I opened a new issue 🐛 Duplicate filters for admins and no shs for anonymous Needs review about it.

  • 🇺🇸United States tyler-durden

    The patch in #12 looks like it will not work with the latest RC4 release, is that correct?

  • 🇺🇸United States tyler-durden

    I was able to get patch #12 to apply to 10.0.7 with no issues, but when adding a taxonomy filter to a Search Index view, it does not go the the next settings screen and I have this error in my records.

    Drupal\Component\Plugin\Exception\PluginException: Plugin (search_api_term) instance class "SearchApiShsTaxonomyIndexTid" does not exist. in Drupal\Component\Plugin\Factory\DefaultFactory::getPluginClass() (line 97 of web/core/lib/Drupal/Component/Plugin/Factory/DefaultFactory.php).

    I cleared cache but that doe snot help, any other suggestions? Thanks!

  • The patch #12 did the job on Drupal 10.2.6.

  • 🇫🇮Finland heikkiy Oulu

    Tested this patch also and it seems to work fine. One small issue I did notice is that in the normal dropdown widgets the All / Any option is first option in the select list. But in the SHS widget the Any option is last in the select list.

    So basically the select list code looks like this:

    <select>
    <option value="1">Term 1</option>
    <option value="2">Term 2</option>
    <option value="All">- Any -</option>
    </select>
    

    If I have several exposed filters in the same view, it's a bit weird UX that in some of them the All option is first and in some it's the last.

  • 🇸🇬Singapore anish.a Singapore

    Any pointers to fix the issue where -Any- appears last?

  • Status changed to RTBC 4 months ago
  • 🇸🇬Singapore anish.a Singapore

    The issue raised by heikkiy is already addressed by issue #3269746. This works fine and can be merged.

  • 🇫🇮Finland heikkiy Oulu

    Thank you @anisha. I failed to find that issue when searching for the issue list and it does indeed fix the issue.

Production build 0.71.5 2024