Registro de cambios

4.2.0

• New feature: The search form shortcode has a new parameter dropdown which can be used to add a category dropdown, like this: [searchform dropdown="category"].
• New feature: Relevanssi can now use the contents of the PDF files indexed with WP File Download.
• New filter: relevanssi_indexing_tokens can be used to filter the tokens (individual words) before they are indexed.
• Removed filter: relevanssi_default_meta_query_relation did not have any effect anymore.
• Changed behaviour: The default taxonomy relation was set to AND in 4.1.4, but wasn’t properly applied before. Now it is really switched.
• Changed behaviour: New post types have been added to list of forbidden post types Relevanssi won’t show as indexing options (ACF, TablePress and WooCommerce).
• Major fix: Tax query processing has been completely refactored, eliminating all sorts of bugs, especially with various edge cases.
• Major fix: Gutenberg block indexing only worked with the Gutenberg plugin enabled. It now works with WP 5.0 built-in Gutenberg as well. If you use Gutenberg blocks, reindex to get all the block content in the index.
• Major fix: Excerpt-building and highlighting did not respect the «Keyword matching» setting. They do now, and the excerpts should be better now.
• Major fix: AND searches needed queries that could get too long for the database to handle. This has been fixed and optimized.
• Major fix: Taxonomy term subquery relations didn’t work; now they are applied.
• Minor fix: iOS uses curly quotes by default, and that didn’t work as a phrase operator. Now phrase operator works with curly quotes and straight quotes.
• Minor fix: The Did you mean broke with search terms longer than 255 characters.
• Minor fix: Phrases with numbers and one word like «team 17» didn’t work, because numbers weren’t counted as words.

4.1.4

• EXISTS and NOT EXISTS didn’t work for taxonomy terms in searches.
• WPML post type handling has been improved. If post type allows fallback for default language, Relevanssi will support that.
• Relevanssi now reminds you to set up automatic trimming for the logs. It’s a really good idea, otherwise the logs will become bloated, which will hurt search performance.
• The Groups posts filter is only applied to public posts to avoid drafts being shown to people who shouldn’t see them.
• The posts_per_page query variable didn’t work; it’s now added to the introduced query variables so that it works.
• Relevanssi won’t log empty queries anymore.
• The default tax query relation was switched from OR to AND to match the WP_Query default behaviour.
• When used with WP 5.1, Relevanssi will now use wp_insert_site instead of the now-deprecated wpmu_new_blog.
• Multisite blog creation is handled better in WP 5.1+.
• Relevanssi now supports Restrict Content Pro permissions.

4.1.3

• Improvements to meta key sorting.
• Relevanssi settings page won’t let you exclude categories you have restricted the search to.
• Members plugin compatibility has been improved: it’s only used if the ‘content permissions’ feature has been enabled.
• The excerpt settings page was a bit buggy.
• Slimstat analytics is now added to the blocked shortcodes list.
• New filter: relevanssi_search_form works exactly like get_search_form, but only applies to the Relevanssi shortcode search forms.
• New JetPack taxonomies and post types have been added to the block list so they won’t appear in Relevanssi settings.

4.1.2

• Choosing «CSS Style» for highlighting was not possible. That is now fixed.
• Gutenberg reusable block indexing was fatally broken with the latest Gutenberg version. That has been updated.
• Relevanssi now by default respects the WooCommerce «exclude from search» setting.
• post__not_in still didn’t work properly, it does now.
• New filter: relevanssi_comparison_order can be used to define the sorting order when sorting the results by post type.
• «Did you mean» process included a very slow query. It is now cached, leading in some cases to massive performance improvements (we’re talking about several seconds here).
• Highlights inside code and similar blocks are handled better now.

4.1.1.2

• Fixes the broken User searches page.

4.1.1.1

• Adding the missing Gutenberg compatibility file.

4.1.1

• Relevanssi can now index Gutenberg reusable blocks. (This functionality broke once already before release, so that can happen, since Gutenberg is still in very active development.)
• The post__in and post__not_in parameters didn’t work, and are now fixed. post_parent__in and post_parent__not_in are also improved.
• You can use named meta queries for sorting posts. Meta query sorting is improved in other ways as well.
• Log export didn’t work properly.
• Adding stopwords from the common word list has been fixed.
• The relevanssi_get_words_having filter hook is now also applied to the free version Did you mean queries.
• New filters: relevanssi_1day and relevanssi_7days can be used to adjust the number of days for log displays, so instead of 1, 7 and 30 days you can have anything you want.

4.1.0.1

• Actually working admin search.

4.1

• New feature: You can now export the search log as a CSV file.
• New feature: Admin Search page allows you to perform searches in WP admin using Relevanssi.
• New filter: relevanssi_admin_search_capability can be used to adjust who sees the admin search page.
• New filter: relevanssi_entities_inside_pre and relevanssi_entities_inside_code adjust how HTML entities are handled inside pre and code tags.
• Numeric meta values (meta_value_num) are now sorted as numbers and not strings.
• Pinned posts have $post->relevanssi_pinned set to 1 for debugging purposes, but you can also use this for styling the posts in the search results templates.
• The Did you mean feature has been toned down a bit, to make the suggestions slightly less weird in some cases.
• Post parent parameters now accept 0 as a value, making it easier to search for children of any post or posts without a parent.
• Polylang compatibility has been improved.
• Phrases with apostrophes inside work better.
• The relevanssi_excerpt filter hook got a second parameter that holds the post ID.
• Custom field sorting actually works now.
• WP Search Suggest compatibility added.