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.
- There’s a problem with WooCommerce 4.4. This is fixed by 2.10.1 and 4.8.1.
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
true. See information here.
- New filter hook
relevanssi_term_wherelets 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_alphabetcan 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.
relevanssi_index_custom_fieldsfilter 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.
- 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.
- Content wrapped in the
noindextags is no longer used for excerpts.
[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
strcasecmp(), leading to more natural results with strings that include numbers.
- Relevanssi init is now moved from priority 10 to priority 1 on the
inithook to avoid problems with missing TablePress compatibility.
- 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.
- 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
initpriority 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 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.