The 3.3.8 update for free Relevanssi matches Relevanssi Premium 1.13.2 and is a maintenance release and generally recommended, as it fixes minor bugs and a possible XSS vulnerability.
- Fixed a bug that caused the results to change depending of the order of words in a multi-word search query.
- Added
product_categoriesandrecent_productsfrom WooCommerce to the list of blocked shortcodes. - There are improvements in excerpt-building and highlighting, especially when fuzzy search is enabled.
- Fixed a possible (if quite unlikely) XSS vulnerability.
- Improved search performance (thanks to MikeNGarrett).
- Sometimes highlights in documents make the document content disappear. I don’t know why, but I’ve added a fix that should make the content visible (without the highlights) if a problem appears.
The XSS vulnerability is related to stopwords: the list of stopwords is printed out unescaped on the Relevanssi settings page in WP admin dashboard. There’s some potential for a XSS vulnerability there, but in order to attack this way, the attacker needs to have admin rights to your WP site in the first place. 1.13.2 fixes the vulnerability in any case.
We are using Relevanssi as a search engine for our site. However, it doesn’t seem to find numbers with an underscore inbetween. For example, if my post contains 2_46, and I try to search for 2_46, I get no results. I do get results if I just enter 46, but the combinations of number and underscore is a token that people will search for. Any ideas on how to make this work? Thanks.
You need to make Relevanssi keep the underscores. The instructions are here (for hyphens and ampersands, but just change the hyphen to an underscore): https://www.relevanssi.com/knowledge-base/words-ampersands-cant-found/
Thank you so much! I had found that page, but wasn’t sure it applied. I now see that it does, and it worked perfectly! Much appreciation to you.