Clarify the module's behavior with SearchAPI filters

Created on 28 June 2024, 6 months ago
Updated 13 September 2024, 3 months ago

Problem/Motivation

I spent quite a lot of time walking through the code and learning how the entire module was coded, only to be stumped why the filter would only work on a small subset of possible values.

Proposed resolution

Add clarification to the README.md file that informs site builders of the possible issues surrounding the SearchAPI fields. The issue has already been addressed and deemed not a bug, but does cause a seriously confusing situation for site builders.

https://www.drupal.org/project/selective_better_exposed_filters/issues/3... πŸ› SearchAPI setItemsPerPage Closed: works as designed

User interface changes

None

API changes

None

Data model changes

None

πŸ“Œ Task
Status

Active

Version

3.0

Component

Documentation

Created by

πŸ‡ΊπŸ‡ΈUnited States ChrisZwemke Portland, OR

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

Merge Requests

Comments & Activities

  • Issue created by @ChrisZwemke
  • I think it's also worth documenting in the form or the README the fact that making use of the "Show only used items" option will load the entire result set, which is a bit inefficient and can potentially lead to performance issues depending on if the site has thousands of results or not.

    I think a better approach might be to alter and build up a custom query that returns only the used terms. It might require more configuration on the user's end to facilitate this, but the performance gain will be very noticeable.

    The alternative is to use Facets instead if you have thousands of results, but again, these disclaimers are probably worth documenting somewhere.

Production build 0.71.5 2024