Skip to main contentSkip to footer

2.30.2

Version 2.30.1 could cause fatal errors in rare circumstances.

  • Minor fix: Fix errors from pinning queries.

2.30.1 / 4.27.1

The meta query security fix failed to acknowledge the wide variety of meta queries possible, causing occasional warnings and possibly even fatal errors.

  • Minor fix: Remove complaints from meta_queries.
  • Premium. Minor fix: Improvements in handling synonyms for multisite missing terms lists.

2.30 / 4.27

Versions 2.30 (Premium) and 4.27 (free) include a bunch of new features and bug fixes. The biggest bug fix is related to multisite searching, where the post weights weren’t calculated correctly before.

There’s also a small security fix related to meta queries using regular expressions, which matters when Relevanssi is used with Relevanssi Live Ajax Search.

  • Premium. New feature: Relevanssi now has a speech-to-text support using the Web Speech API.
  • Premium. New feature: Spam blocking now has a search query length filter that can block too long queries as spam.
  • Premium. New feature: You can now enable automatic search term spelling correction from the settings.
  • New feature: Setting to disable all post_type parameters to let Relevanssi control the post types in the search.
  • New feature: New filter hook relevanssi_truncate_search_queries can be used to truncate search queries to a certain length to eliminate too long queries.
  • New feature: New shortcode  makes it easier to add a “Did you mean” suggestion on a search results page without modifying the template code.
  • New feature: New filter hook relevanssi_allow_meta_query_regexp allows REGEXP or NOT REGEXP meta queries. They are blocked by default for security reasons.
  • Premium. Changed behaviour: Multisite searching is now more in line with the single site search and supports the ‘missing terms’ feature and the + and – operators.
  • Premium. Major fix: The post weights weren’t calculated correctly in multisite searches.
  • Premium. Minor fix: Empty post part targets caused PHP errors. Now they are ignored.
  • Premium. Minor fix: Uninstalling Relevanssi Premium when the free version is active now only uninstalls Premium features.
  • Premium. Minor fix: Spelling corrections work more reliably when the search query involves accents.
  • Minor fix: Relevanssi now clears the scheduled actions on deactivation, not on uninstall.
  • Minor fix: Much faster response for the indexed custom field list.
  • Minor fix: You can now assign anonymous functions to the relevanssi_indexing_restriction filter hook.

Your account

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

Search

Popular Resources

Searching between dates
If you want to have a search with a date range, that’s possible with Relevanssi. It takes a bit of…
Gutenberg Full Site Editing

…excerpts are passed through wp_trim_words() which removes HTML tags. This function can be used to overcome this limitation: add_filter( ‘wp_trim_words’, function( $text, $num_words, $more, $original_text ) { global $post; if ( isset( $post->relevance_score ) ) { return $post->post_excerpt; } return $text; }, 10, 4 ); If the post has the……$more, $original_text ) { global $post; if ( ! empty( $text ) && isset( $post->relevance_score ) ) { return $post->post_excerpt; } return $text; }, 10, 4 ); Restrictions Relevanssi cannot add the highlight parameter to the permalinks in FSE themes. This means you cannot use the “Highlight in documents” feature….…relevance_score attribute set – which should only happen within a search context – this function will cause the wp_trim_words() to return the original post excerpt. With Max Mega Menu, the function above will add the excerpts to the menu items. You can avoid that: add_filter( ‘wp_trim_words’, function( $text, $num_words, $more,…

Related Posts:

Comment Section:

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