Posted on

Premium 1.12

Relevanssi Premium catches up with the free version with this release. As this version removes many bugs and fixes a vulnerability, it is highly recommended to all users.

  • Relevanssi now automatically treats ‘ß’ as ‘ss’. If your site has ‘ß’ in text, reindexing the database is a good idea.
  • Query variable post_status is now supported.
  • Improvements to excerpts: excerpts with phrases work much better now, and the excerpt creation logic has been improved: the excerpts are now better. The process takes a bit more time, though.
  • Allowing HTML tags in excerpts could lead to those tags being left open. Relevanssi will now try to close open HTML tags in excerpts.
  • Allowed tags were not controlled in comments. They are now.
  • Highlighting in documents didn’t always work; it should be more reliable now.
  • Non-integer values are removed from post__in and post__not_in before processing them.
  • Query variables p and page_id are now supported.
  • Relevanssi now understands date_query variables as well.
  • The original post excerpt is stored in $post->original_excerpt.
  • Taxonomy search works better with term id parameters (for example from wp_category_dropdown).
  • Errors about $wpdb->prepare() missing an argument removed.
  • New functions: relevanssi_the_title() and relevanssi_get_the_title() can be used to display highlighted titles in search results.
  • The old title highlighting method has been disabled, because it caused highlights in wrong places. Now the highlighted title is stored in $post->highlighted_post_title, take it from there or use the Relevanssi title functions to display it.
  • Polylang and WPML support was adjusted to perform better in edge cases.
  • Indexing is faster, thanks to some improved code from Tom Novelli.
  • MySQL injection attack vulnerability removed.
  • The cache feature is now removed. Relevanssi should automatically drop the cache tables.
  • New filter: relevanssi_indexing_data lets you modify the data before it’s indexed.
  • Fix for a bug that sometimes caused multisite hits to come from the wrong site.

Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.