Skip to main contentSkip to footer

Version 2.1.4 fixes couple of small bugs – a small regression, a problem sanitizing user inputs, issues with highlighting – and adds one new feature. There’s now a “Pin this post for all keywords” checkbox in the Relevanssi post controls box. That checkbox does pretty much what it says: it pins the post for all keywords that are in the post. Whenever a search is made where the post is found, it will be pinned to the top of the results.

Another significant fix is related to AND searches. There have been cases where a multi-word searches return different results depending on the word order: with certain orders, some posts haven’t been found. That has happened when there’s a throttle involved and some words are very rare. Putting the rare words first has returned results, but with the rare words last nothing is found.

Now Relevanssi will always sort the search terms in the order of rarity, no matter what order the user used. That should guarantee all posts are found as necessary.

  • Fixed cases where Relevanssi added an ellipsis even if the excerpt was from the start of the post.
  • Highlighting now works with numeric search strings.
  • Improved highlighting for accented words. Thanks to Paul Ryan.
  • A surplus comma at the end of post exclusion setting won’t break the search anymore.
  • Fixed instructions for adjusting the throttle limit.
  • New “Pin this post for all keywords” feature.
  • Improved results for AND searches.

The new version is available with the automatic updates, or from the Download page.

Your account

Not logged in. Log in to see your license details.

Search

Popular Resources

Proximity sorting

Relevanssi Premium 2.16 added proximity sorting to search results. That means you can sort the search results by geographic location. Instead of having the most relevant matches first, you can have the nearest results first. There are many ways to use geolocation in WordPress. The way Relevanssi does this is…

Toolset Views

…you’d expect. Because of the way the Toolset Relevanssi compatibility is built, the query variables are not passed to Relevanssi from the search query like they are when Toolset is not involved. This may lead to confusion, when adding a query variable (for example &post_types=page) to the URL has no……effect on the results, even though you can tell for sure the search is powered by Relevanssi. The reason is simple: Relevanssi doesn’t see that query variable, because Toolset does not pass it to Relevanssi. Fortunately Toolset provides means to fix this. There’s a filter hook you can use to…

Related Posts:

Currently there are no related posts available.

Comment Section:

2 Comments. Leave new

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.
You need to agree with the terms to proceed