Skip to main contentSkip to footer

Versions 2.1.6 and 4.0.10 are privacy updates, adding GDPR and privacy-related features to support the new privacy tools in WordPress 4.9.6.

The versions also include bug fixes around places and refactoring to make the code easier to understand if you ever need to look under the hood.

Here’s the complete list of changes:

  • Privacy: If you log search queries, Relevanssi will suggest some additional content to your privacy policy page.
  • Privacy: Relevanssi now supports the new Privacy Policy and Personal Data tools in WordPress 4.9.6.
  • Improved Polylang support. Now taxonomy terms can be language filtered as well.
  • Saving synonyms with quotes worked, but the synonyms showed up wrong.
  • Relevanssi could in some situations override navigation menu links with links to the user profiles or taxonomy terms found in the search. This update fixes that behaviour.
  • Random order works again; using orderby rand didn’t work properly. The rand(seed) format is also supported now.
  • Fixed quotes and apostrophes in Did you mean suggestions.
  • Premium: Taxonomy term indexing had a bug where the type column for taxonomy terms would be set to 0.
  • Premium: The relevanssi_user_index_ok filter is now applied when users are updated.

The free version will be available shortly from the plugin repository. The Premium is already available from the auto-updates if you have the API key in place, and you can also get it from the Download page.

Update 29.5.2018: A bug in 2.1.6 and 4.0.10 causes the admin pages to throw a notice with specific Relevanssi configurations. The plugin also causes a blank page in admin with WP versions older than 4.9.6. Versions 2.1.6.1 and 4.0.10.1 that fix the issue are already out.

Your account

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

Search

Popular Resources

PSA: New ransom scam in town
We were threatened with a new ransom extortion message. I haven’t seen this one before, looks like it’s new but…
Problems with highlighting in post content

…content is passed through the wp_kses_post() function which strips out the malicious content, but also useful content. The easy solution for these problems is to disable the “Highlight query terms in documents” setting. I don’t think it is all that useful in most cases, and all good browsers have an……efficient in-page search feature that can be used to find the matching content. Another option is to adjust the wp_kses_post() functionality with the wp_kses_allowed_html filter hook. If you need to allow CSS styles, for example, you can use this snippet: add_filter( ‘wp_kses_allowed_html’, function( $html, $context ) { if ( ‘post’……a specific page, you can disable the highlighting feature on that page only: add_action( ‘wp_head’, function() { if ( is_page( 123 ) ) { remove_filter( ‘the_content’, ‘relevanssi_highlight_in_docs’, 11 ); } } ); This checks the current page ID and if it’s 123, unhooks the filter function that adds the highlighting….

Related Posts:

Currently there are no related posts available.

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