Registro de cambios

4.8.3

• New feature: Both relevanssi_fuzzy_query and relevanssi_term_where now get the current search term as a parameter.
• 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.

4.8.2

• New feature: New filter hook relevanssi_term_where lets you filter the term WHERE conditional for the search query.
• Minor fix: 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.
• Minor fix: Phrase matching has been improved to make it possible to search for phrases that include characters like the ampersand.

4.8.1

• Major fix: Changes in WooCommerce 4.4.0 broke the Relevanssi searches. This makes the WooCommerce search work again.
• Minor fix: Excluding from logs didn’t work if user IDs had spaces between them (‘user_a, user_b’). Now the extra spaces don’t matter.
• Minor fix: 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.
• Minor fix: Relevanssi indexing procedure was triggered for autosaved drafts, causing possible problems with the asynchronous doc count action.
• Minor fix: 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.

4.8.0

• Changed behaviour: Relevanssi now requires PHP 7.
• Changed behaviour: Relevanssi now sorts strings with strnatcasecmp() instead of strcasecmp(), leading to a more natural results with strings that include numbers.
• Changed behaviour: Relevanssi init is now moved from priority 10 to priority 1 on the init hook to avoid problems with missing TablePress compatibility.
• New feature: New filter hook relevanssi_get_approved_comments_args filters the arguments to get_approved_comments in comment indexing. This can be used to index custom comment types, for example.
• New feature: Content wrapped in the noindex tags is no longer used for excerpts.
• New feature: The [et_pb_fullwidth_code] shortcode is now removed completely, including the contents, when Relevanssi is indexing and building excerpts.
• Major fix: Relevanssi didn’t index new comments when they were added; when a post was indexed or the whole index rebuilt, comment content was included. We 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 fix: Autoload has been disabled for several options that are not needed often.
• Minor fix: Phrase matching did not work correctly in visible custom fields.
• Minor fix: 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.
• Minor fix: The doc count update, which is a heavy task, is now moved to an asynchronous action to avoid slowing down the site for users.
• Minor fix: Relevanssi only updates doc count on relevanssi_insert_edit() when the post is indexed.

4.7.2

• Minor fix: Media Library searches failed if Relevanssi was enabled in the WP admin, but the attachment post type wasn’t indexed. Relevanssi will no longer block the default Media Library search in these cases.
• Minor fix: Adds more backwards compatibility for the relevanssi_indexing_restriction change, there’s now an alert on indexing tab if there’s a problem.

4.7.1

• New feature: New filter hook relevanssi_post_content_after_shortcodes filters the post content after shortcodes have been processed but before the HTML tags are stripped.
• Minor fix: Adds more backwards compatibility for the relevanssi_indexing_restriction change.

4.7.0

• New feature: New filter hook relevanssi_admin_search_blocked_post_types makes it easy to block Relevanssi from searching a specific post type in the admin dashboard. There’s built-in support for Reusable Content Blocks rc_blocks post type, for example.
• New feature: The reason why a post is not indexed is now stored in the _relevanssi_noindex_reason custom field.
• Changed behaviour: The relevanssi_indexing_restriction filter hook has a changed format. Instead of a string value, the filter now expects an array with the MySQL query in the index ‘mysql’ and a reason in string format in ‘reason’. There’s some temporary backwards compatibility for this.
• Changed behaviour: Relevanssi now applies minimum word length when tokenizing search query terms.
• Changed behaviour: Content stopwords are removed from the search queries when doing excerpts and highlights. When Relevanssi uses the untokenized search terms for excerpt-building, stopwords are removed from those words. This should lead to better excerpts.
• Minor fix: Improves handling of emoji in indexing. If the database supports emoji, they are allowed, otherwise they are encoded.

4.6.0

• Changed behaviour: Phrases in OR search are now less restrictive. A search for ‘foo «bar baz»‘ used to only return posts with the «bar baz» phrase, but now also posts with just the word ‘foo’ will be returned.
• Minor fix: User Access Manager showed drafts in search results for all users. This is now fixed.