Relevanssi Premium - The WordPress Search Plugin You Need

Relevanssi Premium - The WordPress Search Plugin You Need v2.27.4.1

No permission to download
Decryption key:


= v2.27.4.1 =
* Minor fix: Remove the update nag.
Decryption key:


* Minor fix: Make click-tracking code more error-resistant.
* Minor fix: Avoid problems with object custom field values.
* Minor fix: Fix problems with click-tracking, pinning and WPML support.
Decryption key:


* Minor fix: Version 2.26.1 had broken the auto updates. This version fixes it.
Decryption key:

This version includes bug fixes, small quality-of-life improvements, and a small security fix. In earlier versions, Relevanssi included password-protected posts in the search results. This can be used to glean information about the posts’ contents. Since I know so
Decryption key:


* New feature: New filter hook `relevanssi_forbidden_post_types` filters the list of post types excluded from Relevanssi indexing.
* New feature: New filter hook `relevanssi_forbidden_taxonomies` filters the list of taxonomies excluded from Relevanssi indexing.
* New feature: New filter hook `relevanssi_show_password_protected` controls whether password protected posts are shown in the search results.
* New feature: The Relevanssi metabox has new CSS classes and added HTML tags to allow better styling and to make it easier to hide sections of the metabox.
* New feature: Relevanssi settings tabs have more CSS ids to help hide individual settings.
* New feature: Support for `post_mime_type` query parameter.
* Changed behaviour: The `pre_relevanssi_related` and `post_relevanssi_related` action hooks get the post ID as a parameter, as it's not always available otherwise.
* Changed behaviour: Password protected posts are excluded from the search results by default to protect their contents.
* Minor fix: Click-tracking front end JS code now uses `wp_print_inline_script_tag()`.
* Minor fix: Related posts template CSS now uses `wp_add_inline_style()`.
* Minor fix: An array `_rt` tag won't cause a fatal error anymore.
* Minor fix: The Relevanssi network options blog list is reduced to 50 blogs to avoid crashes.
* Minor fix: The settings tab query parameter was renamed to avoid collisions with other plugins.
* Minor fix: The `post_id` parameter in the `[relevanssi_related_posts]` shortcode didn't work.
* Minor fix: In rare cases, the search results would not be in relevance order if the throttle wasn't used.
Decryption key:


  • Security fix: Prevent CSV injection attack in log export. This has no effect, unless you export logs to view them in a spreadsheet app, and even there I’m not sure what damage can be done.
  • Security fix: Restrict access to doc count updates. This could’ve been used as a method for denial-of-service attacks; of course, it’s just one of many such methods to attack a WordPress site, with or without Relevanssi.
  • Minor fix: Product variations check the parent product for access restrictions to avoid situations where variations of a draft product appear in the results.
  • Minor fix: Improved TablePress compatibility.
  • Minor fix: Added error handling to the Ninja Table compatibility code.

2.25.1 / 4.22.1​

  • Security fix: Relevanssi had a vulnerability where anyone could access search and click logs. The log export is now protected.
  • Minor fix: Relevanssi had problems with Polylang when a post or term didn’t specify a language. Now Relevanssi handles those situations better.
  • Minor fix: Post date throttling had a MySQL error that made it replace JOINs instead of concatenating.
  • Minor fix: The log database table now has an index on session_id, as not having that index can greatly slow down the search.
== Changelog ==

= 2.24.4 =
* Minor fix: Fixes broken taxonomy indexing.
== Changelog ==

= 2.24.4 =
* Minor fix: Fixes broken taxonomy indexing.
== Changelog ==

v2.24.2 / 4.21.2
  • Premium. Minor fix: Fixes broken WP CLI progress bars.
  • Premium. Minor fix: For indexing, the stemmer is always in OR mode so that both the stemmed and original words are indexed.
  • Minor fix: Meta query boolean to array conversion.

About us

  • Our community has been around for many years and pride ourselves on offering unbiased, critical discussion among people of all different backgrounds. We are working every day to make sure our community is one of the best.

Quick Navigation

User Menu