BUG? Different Custom Search Results should not interfere with each other.

Open
#2,180 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
elasticsearch, php
Domain
backend, search

Research direction

Start by reproducing the two Custom Search Results case described in the issue and trace how their result matching is handled. Add regression coverage for the substring case; done means results assigned to one Custom Search Result no longer appear in the other.

Written by the indexing model from the issue text.

Description

enhancement module:custom-search-results

Describe the bug

If a user has two different Custom Search Results and one is a substring of the other, results in the smaller one will appear in the longest one.

Example: "Dental Real Estate Purchases" and "Real Estate". While searching for "Real Estate", the results added to "Dental Real Estate Purchases" will show up as "Real Estate" matches the search term.

Steps to Reproduce

  1. Create two different CSR: "Dental Real Estate Purchases" and "Real Estate"
  2. Add a post to "Dental Real Estate Purchases"
  3. Search for "Real Estate"
  4. See the post added to "Dental Real Estate Purchases" in the results

Expected behavior

Should the results added to one CSR be displayed in another one?

Dominant language
PHP
Stars
1.3k
Forks
325
Avg merge
2d 11h
Merged PRs (30d)
24

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from 10up/ElasticPress

All issues in 10up/ElasticPress

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.