Posted on

Premium 2.10 / Free 4.8

After the Summer break, Relevanssi is back with new versions, both to Premium and free. These are mostly small improvements, but when testing the new version, I discovered a bug in the comment indexing that has made Relevanssi not index comments when they are added. I’m not sure why this hasn’t come up in tests before this.

Relevanssi also now requires PHP 7. It should not be possible to update Relevanssi on sites that are still running PHP 5. If your site is running PHP 5, it’s badly irresponsible and you really, really should update the PHP version to something more recent immediately.

TL; DR: If you have set Relevanssi to index comments, you need to rebuild the index after updating to make sure all comments are included in the index.

Known issues

  • There’s a problem with WooCommerce 4.4. This is fixed by 2.10.1 and 4.8.1.
  • The post_relevanssi_related action hook does not fire, which may cause surprising changes in the plugin settings if the pre_relevanssi_related hook is used to adjust things. This is fixed by 2.10.3.
  • Excluding posts from block editor does not work. This will be fixed in the version 2.11.

2.10.3 / 4.8.3

  • (Premium) New feature: Multisite searching now supports date parameters.
  • New feature: Both relevanssi_fuzzy_query and relevanssi_term_where now get the current search term as a parameter.
  • New feature: New filter hook relevanssi_tabs can be used to adjust the tabs in Relevanssi settings page to add, modify or delete the tabs.
  • (Premium) Major fix: The post_relevanssi_related action hook did not fire at all, causing possible problems if pre_relevanssi_related set something that post_relevanssi_related was supposed clear out. The default behaviour isn’t a problem, but some custom solutions may be.
  • Minor fix: Relevanssi database tables don’t have PRIMARY keys, only UNIQUE keys. In case this is a problem (for example on Digital Ocean servers), deactivate and activate Relevanssi to fix the problem.
  • Minor fix: When posts_per_page was set to -1, the max_num_pages was incorrectly set to the number of posts found. It should, of course, be 1.
  • Minor fix: Excluding from logs didn’t work if user IDs had spaces between them ('user_a, user_b'). This is now fixed for good, the earlier fix didn’t work.
  • (Premium) Minor fix: When indexing, users are now counted in a different way, so that the relevanssi_user_indexing_args filter hook is applied and the count reflects the actual number of users indexed.

2.10.2 / 4.8.2

  • (Premium) Wildcard operators ? (any one letter) and * (zero or more letters) can be used inside words, if enabled by setting the relevanssi_wildcard_search filter to true. See information here.
  • New filter hook relevanssi_term_where lets you filter the term WHERE conditional for the search query.
  • Doing the document count updates asynchronously caused problems in some cases (eg. importing posts). Now the document count is only updated after a full indexing and once per week.
  • Phrase matching has been improved to make it possible to search for phrases that include characters like the ampersand.

2.10.1 / 4.8.1

  • (Premium) New filter hook relevanssi_didyoumean_alphabet can be used to replace the default Latin alphabet with something more suited to your site.
  • Changes in WooCommerce 4.4.0 broke the Relevanssi searches. This makes the WooCommerce search work again.
  • Excluding from logs didn’t work if user IDs had spaces between them (‘user_a, user_b’). Now the extra spaces don’t matter.
  • The asynchronous doc count action in the previous version could cause an infinite loop with the Snitch logger plugin. This is prevented now: the async action doesn’t run after indexing unless a post is actually indexed.
  • Relevanssi indexing procedure was triggered for autosaved drafts, causing possible problems with the asynchronous doc count action.
  • The relevanssi_index_custom_fields filter hook was not applied when doing phrase matching, thus phrases could not be found when they were in custom fields added with the filter.
  • (Premium) Apostrophes in redirect queries didn’t work. That is now fixed and saving a query with an apostrophe works and will redirect.

New features

  • Premium only: Relevanssi now shows a warning when a multisite site is not public, as that will lead to no search results because Relevanssi doesn’t search non-public sites.
  • Premium only: The redirects tab now shows the number of times each redirect has been used.

Changed behaviour

  • Content wrapped in the noindex tags is no longer used for excerpts.
  • The [et_pb_fullwidth_code] shortcode is now removed completely, including the contents, when Relevanssi is indexing and building excerpts.
  • Relevanssi now requires PHP 7.
  • Relevanssi now sorts strings with strnatcasecmp() instead of strcasecmp(), leading to more natural results with strings that include numbers.
  • Relevanssi init is now moved from priority 10 to priority 1 on the init hook to avoid problems with missing TablePress compatibility.

Major fixes

  • Relevanssi didn’t index new comments when they were added; when a post was indexed or the whole index rebuilt, comment content was included. I don’t know how long this bug has existed, but it is now fixed. Rebuild the index to get all comment content included in the index.

Minor fixes

  • Phrase matching did not work correctly in visible custom fields.
  • TablePress support could cause halting errors if posts were inserted before Relevanssi has loaded itself (on init priority 10). These errors will no longer happen.
  • Relevanssi only updates doc count on relevanssi_insert_edit() when the post is indexed.
  • Counting document count is a slow process that has slowed down opening the indexing tab. It’s now done asynchronously. Thanks to Mike Garrett.

The free version is available from the WordPress plugin repository. You can get the Premium version from the Download page or with the automatic update.

The download page shows two different versions of the plugin available. The basic version no longer includes tests or anything else you won’t need when actually using the plugin. The developer version includes tests and all sorts of other tooling you may find interesting if you’re a developer.

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.