plugins - Accounting for search terms that may include a space, using SearchWP

As the title suggest I am having an issue with setting up the plugin SearchWP to correctly work with search terms (product names) that may, or may not, contain spaces. e.g. "ABC1" or "ABC 1".

I am not entirely 100% sure how to approach this issue.

Like terms are not appropriate as it only deals with single words. "ABC 1" would be considered 2 separate words.

Fuzzy logic doesn't appear to achieve the correct results e.g. returning results for "ABC 2" "ABC 3" ABC 4".

I have tried the approach of a custom field of search synonyms for each product. Again that hasn't had the desired results either.

Any advice or guidance on this matter would be greatly appreciated.

Many thanks

As the title suggest I am having an issue with setting up the plugin SearchWP to correctly work with search terms (product names) that may, or may not, contain spaces. e.g. "ABC1" or "ABC 1".

I am not entirely 100% sure how to approach this issue.

Like terms are not appropriate as it only deals with single words. "ABC 1" would be considered 2 separate words.

Fuzzy logic doesn't appear to achieve the correct results e.g. returning results for "ABC 2" "ABC 3" ABC 4".

I have tried the approach of a custom field of search synonyms for each product. Again that hasn't had the desired results either.

Any advice or guidance on this matter would be greatly appreciated.

Many thanks

• plugins
• search

Share Improve this question asked Jan 23, 2019 at 12:22 noelmcgnoelmcg 19911 silver badge1212 bronze badges 5

• SearchWP uses its own search engine, so any questsions about how it works should be directed to the plugin author/support community. It doesn't really have anything to do with WordPress development. – Jacob Peattie Commented Jan 23, 2019 at 12:39
• @JacobPeattie Apologies, I had a feeling that might be an issue. Unfortunately they appear to have closed their support forum and there isn't any presence on wordpress. StackExchange was my next bet. – noelmcg Commented Jan 23, 2019 at 12:45
• Sorry, I can contact the plugin author. Cheers