Descrizione

Relevanssi replaces the standard WordPress search with a better search engine, with lots of features and configurable options. You’ll get better results, better presentation of results – your users will thank you.

This is the free version of Relevanssi. There’s also Relevanssi Premium, which has added features, including Multisite support. This free version does not work properly on Multisite. For more information about Premium, see Relevanssi.com.

Key features

Search results sorted in the order of relevance, not by date.
Fuzzy matching: match partial words, if complete words don’t match.
Find documents matching either just one search term (OR query) or require all words to appear (AND query).
Search for phrases with quotes, for example “search phrase”.
Create custom excerpts that show where the hit was made, with the search terms highlighted.
Highlight search terms in the documents when user clicks through search results.
Search comments, tags, categories and custom fields.

Advanced features

Adjust the weighting for titles, tags and comments.
Log queries, show most popular queries and recent queries with no hits.
Restrict searches to categories and tags using a hidden variable or plugin settings.
Index custom post types and custom taxonomies.
Index the contents of shortcodes.
Google-style “Did you mean?” suggestions based on successful user searches.
Automatic support for WPML multi-language plugin.
Automatic support for s2member membership plugin.
Advanced filtering to help hacking the search results the way you want.
Search result throttling to improve performance on large databases.
Disable indexing of post content and post titles with a simple filter hook.

Relevanssi is available in two versions, regular and Premium. Regular Relevanssi is and will remain free to download and use. Relevanssi Premium comes with a cost, but will get all the new features. Standard Relevanssi will be updated to fix bugs, but new features will mostly appear in Premium. Also, support for standard Relevanssi depends very much on my mood and available time. Premium pricing includes support.

Premium features (only in Relevanssi Premium)

Improved spelling correction in “Did you mean?” suggestions.
Multisite support.
Search and index user profiles.
Search and index taxonomy term pages (categories, tags, custom taxonomies).
Search and index arbitrary columns in wp_posts MySQL table.
Assign weights to any post types and taxonomies.
Assign extra weight to new posts.
Let the user choose between AND and OR searches, use + and – operator (AND and NOT).
Highlighting search terms for visitors from external search engines.
Export and import settings.
WP CLI commands.

Relevanssi in Facebook

You can find Relevanssi in Facebook. Become a fan to follow the development of the plugin, I’ll post updates on bugs, new features and new versions to the Facebook page.

Other search plugins

Relevanssi owes a lot to wpSearch by Kenny Katzgrau. Relevanssi was built to replace wpSearch, when it started to fail.

Search Unleashed is a popular search plugin, but it hasn’t been updated since 2010. Relevanssi is in active development and does what Search Unleashed does.

Known issues and To-do’s

Known issue: In general, multiple Loops on the search page may cause surprising results. Please make sure the actual search results are the first loop.
Known issue: Relevanssi doesn’t necessarily play nice with plugins that modify the excerpt. If you’re having problems, try using relevanssi_the_excerpt() instead of the_excerpt().

Thanks

Cristian Damm for tag indexing, comment indexing, post/page exclusion and general helpfulness.
Marcus Dalgren for UTF-8 fixing.
Warren Tape for 2.5.5 fixes.
Mohib Ebrahim for relentless bug hunting.

Installazione

Extract all files from the ZIP file, and then upload the plugin’s folder to /wp-content/plugins/.
If your blog is in English, skip to the next step. If your blog is in other language, rename the file stopwords in the plugin directory as something else or remove it. If there is stopwords.yourlanguage, rename it to stopwords.
Activate the plugin through the ‘Plugins’ menu in WordPress.
Go to the plugin settings and build the index following the instructions there.

To update your installation, simply overwrite the old files with the new, activate the new version and if the new version has changes in the indexing, rebuild the index.

Note on updates

If it seems the plugin doesn’t work after an update, the first thing to try is deactivating and reactivating the plugin. If there are changes in the database structure, those changes do not happen without a deactivation, for some reason.

Changes to templates

None necessary! Relevanssi uses the standard search form and doesn’t usually need any changes in the search results template.

If the search does not bring any results, your theme probably has a query_posts() call in the search results template. That throws Relevanssi off. For more information, see The most important Relevanssi debugging trick.

How to index

Check the options to make sure they’re to your liking, then click “Save indexing options and build the index”. If everything’s fine, you’ll see the Relevanssi options screen again with a message “Indexing successful!”

If something fails, usually the result is a blank screen. The most common problem is a timeout: server ran out of time while indexing. The solution to that is simple: just return to Relevanssi screen (do not just try to reload the blank page) and click “Continue indexing”. Indexing will continue. Most databases will get indexed in just few clicks of “Continue indexing”. You can follow the process in the “State of the Index”: if the amount of documents is growing, the indexing is moving along.

If the indexing gets stuck, something’s wrong. I’ve had trouble with some plugins, for example Flowplayer video player stopped indexing. I had to disable the plugin, index and then activate the plugin again. Try disabling plugins, especially those that use shortcodes, to see if that helps. Relevanssi shows the highest post ID in the index – start troubleshooting from the post or page with the next highest ID. Server error logs may be useful, too.

Using custom search results

If you want to use the custom search results, make sure your search results template uses the_excerpt() to display the entries, because the plugin creates the custom snippet by replacing the post excerpt.

If you’re using a plugin that affects excerpts (like Advanced Excerpt), you may run into some problems. For those cases, I’ve included the function relevanssi_the_excerpt(), which you can use instead of the_excerpt(). It prints out the excerpt, but doesn’t apply wp_trim_excerpt() filters (it does apply the_content(), the_excerpt(), and get_the_excerpt() filters).

To avoid trouble, use the function like this:

<?php if (function_exists('relevanssi_the_excerpt')) { relevanssi_the_excerpt(); }; ?>

See Frequently Asked Questions for more instructions on what you can do with Relevanssi.

The advanced hacker option

If you’re doing something unusual with your search and Relevanssi doesn’t work, try using relevanssi_do_query(). See Knowledge Base.

Uninstalling

To uninstall the plugin remove the plugin using the normal WordPress plugin management tools (from the Plugins page, first Deactivate, then Delete). If you remove the plugin files manually, the database tables and options will remain.

Combining with other plugins

Relevanssi doesn’t work with plugins that rely on standard WP search. Those plugins want to access the MySQL queries, for example. That won’t do with Relevanssi. Search Light, for example, won’t work with Relevanssi.

Some plugins cause problems when indexing documents. These are generally plugins that use shortcodes to do something somewhat complicated. One such plugin is MapPress Easy Google Maps. When indexing, you’ll get a white screen. To fix the problem, disable either the offending plugin or shortcode expansion in Relevanssi while indexing. After indexing, you can activate the plugin again.

FAQ

Installation Instructions

Extract all files from the ZIP file, and then upload the plugin’s folder to /wp-content/plugins/.
If your blog is in English, skip to the next step. If your blog is in other language, rename the file stopwords in the plugin directory as something else or remove it. If there is stopwords.yourlanguage, rename it to stopwords.
Activate the plugin through the ‘Plugins’ menu in WordPress.
Go to the plugin settings and build the index following the instructions there.

To update your installation, simply overwrite the old files with the new, activate the new version and if the new version has changes in the indexing, rebuild the index.

Note on updates

Changes to templates

None necessary! Relevanssi uses the standard search form and doesn’t usually need any changes in the search results template.

How to index

Using custom search results

To avoid trouble, use the function like this:

<?php if (function_exists('relevanssi_the_excerpt')) { relevanssi_the_excerpt(); }; ?>

See Frequently Asked Questions for more instructions on what you can do with Relevanssi.

The advanced hacker option

If you’re doing something unusual with your search and Relevanssi doesn’t work, try using relevanssi_do_query(). See Knowledge Base.

Uninstalling

Combining with other plugins

Knowledge Base

You can find solutions and answers at the Relevanssi Knowledge Base.

Relevanssi doesn’t work

If you the results don’t change after installing and activating Relevanssi, the most likely reason is that you have a call to query_posts() on your search results template. This confuses Relevanssi. Try removing the query_posts call and see what happens.

Searching for words with ampersands or hyphens doesn’t work

Please read Words with punctuation can’t be found. This is a Relevanssi feature, but you can circumvent it with a simple filter function.

Where are the user search logs?

See the top of the admin menu. There’s ‘User searches’. There. If the logs are empty, please note showing the results needs at least MySQL 5.

Displaying the number of search results found

The typical solution to showing the number of search results found does not work with Relevanssi. However, there’s a solution that’s much easier: the number of search results is stored in a variable within $wp_query. Just add the following code to your search results template:

<?php echo 'Relevanssi found ' . $wp_query->found_posts . ' hits'; ?>

Advanced search result filtering

If you want to add extra filters to the search results, you can add them using a hook. Relevanssi searches for results in the _relevanssi table, where terms and post_ids are listed. The various filtering methods work by listing either allowed or forbidden post ids in the query WHERE clause. Using the relevanssi_where hook you can add your own restrictions to the WHERE clause.

These restrictions must be in the general format of
AND doc IN (‘ . {a list of post ids, which could be a subquery} . ‘)

For more details, see where the filter is applied in the relevanssi_search() function. This is stricly an advanced hacker option for those people who’re used to using filters and MySQL WHERE clauses and it is possible to break the search results completely by doing something wrong here.

There’s another filter hook, relevanssi_hits_filter, which lets you modify the hits directly. The filter passes an array, where index 0 gives the list of hits in the form of an array of post objects and index 1 has the search query as a string. The filter expects you to return an array containing the array of post objects in index 0 (return array($your_processed_hit_array)).

Direct access to query engine

Relevanssi can’t be used in any situation, because it checks the presence of search with the is_search() function. This causes some unfortunate limitations and reduces the general usability of the plugin.

You can now access the query engine directly. There’s a new function relevanssi_do_query(), which can be used to do search queries just about anywhere. The function takes a WP_Query object as a parameter, so you need to store all the search parameters in the object (for example, put the search terms in $your_query_object->query_vars['s']). Then just pass the WP_Query object to Relevanssi with relevanssi_do_query($your_wp_query_object);.

Relevanssi will process the query and insert the found posts as $your_query_object->posts. The query object is passed as reference and modified directly, so there’s no return value. The posts array will contain all results that are found.

Sorting search results

If you want something else than relevancy ranking, you can use orderby and order parameters. Orderby accepts $post variable attributes and order can be “asc” or “desc”. The most relevant attributes here are most likely “post_date” and “comment_count”.

If you want to give your users the ability to sort search results by date, you can just add a link to http://www.yourblogdomain.com/?s=search-term&orderby=post_date&order=desc to your search result page.

Order by relevance is either orderby=relevance or no orderby parameter at all.

Filtering results by date

You can specify date limits on searches with by_date search parameter. You can use it your search result page like this: http://www.yourblogdomain.com/?s=search-term&by_date=1d to offer your visitor the ability to restrict their search to certain time limit (see RAPLIQ for a working example).

The date range is always back from the current date and time. Possible units are hour (h), day (d), week (w), month (m) and year (y). So, to see only posts from past week, you could use by_date=7d or by_date=1w.

Using wrong letters for units or impossible date ranges will lead to either defaulting to date or no results at all, depending on case.

Thanks to Charles St-Pierre for the idea.

Displaying the relevance score

Relevanssi stores the relevance score it uses to sort results in the $post variable. Just add something like

echo $post->relevance_score

to your search results template inside a PHP code block to display the relevance score.

Did you mean? suggestions

To use Google-style “did you mean?” suggestions, first enable search query logging. The suggestions are based on logged queries, so without good base of logged queries, the suggestions will be odd and not very useful.

To use the suggestions, add the following line to your search result template, preferably before the have_posts() check:

<?php if (function_exists('relevanssi_didyoumean')) { relevanssi_didyoumean(get_search_query(), "<p>Did you mean: ", "?</p>", 5); }?>

The first parameter passes the search term, the second is the text before the result, the third is the text after the result and the number is the amount of search results necessary to not show suggestions. With the default value of 5, suggestions are not shown if the search returns more than 5 hits.

Relevanssi Premium has a much better version of this feature.

Search shortcode

Relevanssi also adds a shortcode to help making links to search results. That way users can easily find more information about a given subject from your blog. The syntax is simple:

[search]John Doe[/search]

This will make the text John Doe a link to search results for John Doe. In case you want to link to some other search term than the anchor text (necessary in languages like Finnish), you can use:

[search term="John Doe"]Mr. John Doe[/search]

Now the search will be for John Doe, but the anchor says Mr. John Doe.

One more parameter: setting [search phrase="on"] will wrap the search term in quotation marks, making it a phrase. This can be useful in some cases.

Restricting searches to categories and tags

Relevanssi supports the hidden input field cat to restrict searches to certain categories (or tags, since those are pretty much the same). Just add a hidden input field named cat in your search form and list the desired category or tag IDs in the value field – positive numbers include those categories and tags, negative numbers exclude them.

This input field can only take one category or tag id (a restriction caused by WordPress, not Relevanssi). If you need more, use cats and use a comma-separated list of category IDs.

The same works with post types. The input fields are called post_type and post_types.

You can also set the restriction from general plugin settings (and then override it in individual search forms with the special field). This works with custom taxonomies as well, just replace cat with the name of your taxonomy.

If you want to restrict the search to categories using a dropdown box on the search form, use a code like this:

<form method="get" action="<?php bloginfo('url'); ?>">
    <div><label class="screen-reader-text" for="s">Search</label>
    <input type="text" value="<?php the_search_query(); ?>" name="s" id="s" />
<?php
    wp_dropdown_categories(array('show_option_all' => 'All categories'));
?>
    <input type="submit" id="searchsubmit" value="Search" />
    </div>
</form>

This produces a search form with a dropdown box for categories. Do note that this code won’t work when placed in a Text widget: either place it directly in the template or use a PHP widget plugin to get a widget that can execute PHP code.

Restricting searches with taxonomies

You can use taxonomies to restrict search results to posts and pages tagged with a certain taxonomy term. If you have a custom taxonomy of “People” and want to search entries tagged “John” in this taxonomy, just use ?s=keyword&people=John in the URL. You should be able to use an input field in the search form to do this, as well – just name the input field with the name of the taxonomy you want to use.

It’s also possible to do a dropdown for custom taxonomies, using the same function. Just adjust the arguments like this:

wp_dropdown_categories(array('show_option_all' => 'All people', 'name' => 'people', 'taxonomy' => 'people'));

This would do a dropdown box for the “People” taxonomy. The ‘name’ must be the keyword used in the URL, while ‘taxonomy’ has the name of the taxonomy.

Automatic indexing

Relevanssi indexes changes in documents as soon as they happen. However, changes in shortcoded content won’t be registered automatically. If you use lots of shortcodes and dynamic content, you may want to add extra indexing. Here’s how to do it:

if (!wp_next_scheduled('relevanssi_build_index')) {
    wp_schedule_event( time(), 'daily', 'relevanssi_build_index' );
}

Add the code above in your theme functions.php file so it gets executed. This will cause WordPress to build the index once a day. This is an untested and unsupported feature that may cause trouble and corrupt index if your database is large, so use at your own risk. This was presented at forum.

Highlighting terms

Relevanssi search term highlighting can be used outside search results. You can access the search term highlighting function directly. This can be used for example to highlight search terms in structured search result data that comes from custom fields and isn’t normally highlighted by Relevanssi.

Just pass the content you want highlighted through relevanssi_highlight_terms() function. The content to highlight is the first parameter, the search query the second. The content with highlights is then returned by the function. Use it like this:

if (function_exists('relevanssi_highlight_terms')) {
    echo relevanssi_highlight_terms($content, get_search_query());
}
else { echo $content; }

What is tf * idf weighing?

It’s the basic weighing scheme used in information retrieval. Tf stands for term frequency while idf is inverted document frequency. Term frequency is simply the number of times the term appears in a document, while document frequency is the number of documents in the database where the term appears.

Thus, the weight of the word for a document increases the more often it appears in the document and the less often it appears in other documents.

What are stop words?

Each document database is full of useless words. All the little words that appear in just about every document are completely useless for information retrieval purposes. Basically, their inverted document frequency is really low, so they never have much power in matching. Also, removing those words helps to make the index smaller and searching faster.

Recensioni

Very useful and great support!

jacquid

I needed a search tool to index shortcode content, which led me to this awesome plugin. It is incredibly efficient, and Pro is even better! Support is outstanding as well. I will be using this in many future projects! Thank you!

Powerfull plugin

chillmen

Must have plugin if you want to boost the search in wp
the plugin is easy to setup and offer many options
i like the user queries logs, did you mean function (pro is even better) and the filter by categories in the search result
i was using the free version for months but it was missing something, i decided to move to the pro version and the experience is completely different
Keep up the good work
thank you

Most better search plugin

track77

Flexible in settings and very useful.
Contains all the necessary wp hooks for those who want to customize it for their needs.

Works with ACF 🙂

robfrancken

At first I wasn’t sure if this would work with Advanced Custom Fields, but then I found the filter which lets you specify which fields to include, and it works flawlessly.

Couldn’t be happier! Thank you Mikko!

Ottimo

sermatica

Ottimo per creare ricerche personalizzate anche se complicato da usare.

Doesn’t search for meta tags

danmiller

Doesn’t search for meta tags

Leggi tutte le 178 recensioni

Contributori & Sviluppatori

“Relevanssi – A Better Search” è un software open source. Le persone che hanno contribuito allo sviluppo di questo plugin sono indicate di seguito.

Mikko Saari

“Relevanssi – A Better Search” has been translated into 5 locales. Grazie ai traduttori per i loro contributi.

Traduci “Relevanssi – A Better Search” nella tua lingua.

Interessato allo sviluppo?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

3.6.0

Changed a bit how Relevanssi attaches itself to queries. Instead of the global $wp_query, Relevanssi now uses the query passed as the parameter to the_posts filter hook. This should improve compatibility in some cases, but may cause problems in some fringe cases. If you’re doing something unusual with Relevanssi, try this out before deploying to public use.
Some meta queries caused major problems with the Relevanssi weighting algorithm. This has now been fixed.
Error notices caused by trying to use a non-existing taxonomy term have been removed.

3.5.12

Post type exclusion didn’t work as expected.
Relevanssi couldn’t handle nested tax queries (such as those generated by WooCommerce product visibility filtering) properly.

3.5.11.1

New filter: relevanssi_allow_one_letter_highlights lets you allow one-letter highlights. Just make the filter function return true.
New filter: relevanssi_block_one_letter_searches by default blocks one-letter searches. If you want to enable them, add a filter function that always returns false.
Fixed an undefined variable notice.

3.5.11

Synonym indexing failed if synonyms contained a forward slash.
Highlighting HTML tags has been improved further.
New filter: relevanssi_tag_before_tokenize allows you to access tag content before indexing.
Relevanssi now actively blocks one-letter search terms, as they are generally pointless and can cause “out of memory” issues. One-letter search terms are no longer highlighted, either. These are usually caused by cases like “word’s” being interpreted as “word s”.
New filter: relevanssi_disable_shortcodes_excerpt lets you add more shortcodes to be disabled before excerpts are built.

3.5.10

Some users got a fatal parse error. That shouldn’t happen anymore.
FacetWP users ran into trouble, as relevanssi_do_query() started to explicitly expect a WP_Query object in version 1.15.0. That expectation is removed; it’s still highly recommended for future compatibility that you use WP_Query objects.
Small bug fix: get_current_screen() is now only used when it’s available to avoid occasional fatal errors.
Error messages from DOING_AJAX being undefined should be removed.

3.5.9.1

WP.org plugin repo didn’t like 3.5.9 for some reason, hoping to have better luck with this.

3.5.9

Improved the way highlighting handles HTML tags, especially when highlighting on post pages.
The throttle limit setting was removed from the settings page for causing trouble. If you need to change it, update relevanssi_throttle_limit option directly.
Relevanssi didn’t support tax_queries with field set to name. That works now.
Much faster way of showing the 25 most common words in the index. If you’ve disabled this feature because it was so slow, try enabling it – you might be surprised!

3.5.8

Did you mean function had a XSS vulnerability, which is now removed.
Minimum word length wasn’t applied to titles in indexing. It is now fixed. If you think this is a problem, rebuild the index.
TablePress compatibility has been improved.
Meta query handling has been improved, thanks to Maxime Culea.
Improved WP_Query parameter support: setting query variable sentence to 1 forces phrase search.
Improved ACF compatibility.

3.5.7.1

Small fix for a bug that broke the settings page.

3.5.7

An improved version of the sorting function will not throw notices when Intuitive Custom Post Order plugin is used.
New filter: relevanssi_missing_sort_key can be used to adjust the result sorting when using keys that are not present in all posts (eg. menu_order).
Czech translation and stopwords, thanks to Michael Kucera.
Relevanssi broke the WP admin menu search when admin searches were enabled.
Relevanssi broke the admin page search under WP 4.7. Relevanssi is now disabled in admin page searches.
The way accented characters are handled in highlighting is improved. A new filter, relevanssi_accents_replacement_arrays, can be used to adjust the accent replacement.

3.5.6.1

Fix for a fatal bug in 3.5.6.

3.5.6

Relevanssi admin page had a vulnerability that allowed SQL injection attacks. That is now fixed.
Relevanssi didn’t like to highlight search terms that are followed by a ?, an ! or an apostrophe.
New filter: relevanssi_ok_to_log lets you control whether search queries are logged or not.

3.5.5

500 errors caused by arrays in custom fields should be gone now.
Improvements to the ACF “select” field support.
Relevanssi will not break when frontend plugins insert posts.
relevanssi_match filter has a new parameter, which contains the search term.
Polylang support has been improved.
WPML and Polylang filters work when “fields” is set to “ids”.
New filter: relevanssi_log_get_user gets passed the user object before Relevanssi decides if the query should be logged or not.

3.5.4

Relevanssi had a bug that lead to inflated relevancy scores for posts.
Relevanssi can now index the human-readable labels of ACF “select” fields. (Thanks to Raphaël Droz.)
New filter: relevanssi_30days can be used to adjust the 30 day logs to a different number of days.
Adding stopwords that contain apostrophes didn’t work.
Ensured PHP7 and WP 4.6 compatibility.
Fixed a small glitch that could happen if a highlighted term is next to a starting square bracket.

3.5.3

New filter relevanssi_user_searches_limit to adjust the number of user searches shown in the logs.
Old data check is only done on Relevanssi settings page, not on all admin pages. That should improve admin performance.
Fixed a fatal error when searching includes private posts.
New filter: relevanssi_remote_addr can be used to modify the IP address logged to Relevanssi logs.
Blocked CFDB and WooCommerce shortcodes that are causing problems with Relevanssi.

3.5.2

Added correct support for term_taxonomy_id in the fields parameter in tax_queries.

3.5.1

Fixed an error in the Did you mean function.
Fixed an error if the search term was not found in content.
Fixed an error when building excerpts from posts shorter than the excerpt length.
Blocked the [starpro] shortcode that was causing problems with Relevanssi.
New filter: relevanssi_remove_stopwords_in_titles allows you to include stopwords in titles.
Added support for term_tax_id in the fields parameter in tax_queries.
Excerpt-building failed if multibyte string operations were missing. It should work now.

3.5

Tokenizer was using strlen() and not mb_strlen(), so word lengths were not calculated properly. If your site uses non-ASCII alphabet, rebuilding the index is a good idea.
Small improvement to WPML multilanguage filtering.
relevanssi_the_title() got a new parameter: if you don’t want to echo the title, you can use it like relevanssi_the_title(false) to make it return the title.
Relevanssi had the_title filter hook calls that were missing the second parameter; that’s now fixed.
The excerpt-building algorithm is completely rewritten based on work by Ben Boyter (http://www.boyter.org/).
The [watupro] shortcode didn’t work with Relevanssi, so Relevanssi will now bypass it.
The plugin i18n features have been improved slightly.
New filter: relevanssi_didyoumean_suggestion lets you modify the Did you mean? suggestion before it’s displayed.
relevanssi_didyoumean() has a new parameter: you can now choose whether the result is echoed out (the default value) or just returned.
In the search results breakdown, you can now use %categories% and %taxonomies% to show the number of matches in categories and taxonomies other than tags and cats, respectively.
Relevanssi supports fields parameter (both ids and id=>parent) to return only post IDs or post IDs and post parents.

3.4.2

Empty lines on synonym settings caused problems. Fixed that.
In WordPress 4.2 installations, emoji in will be handled better. Emoji in posts may cause problems with WordPress versions below 4.2, so please update!

3.4.1

Removed a notice about an undefined variable.

3.4

New filter: relevanssi_valid_admin_status can be used to adjust post statuses that Relevanssi will handle.
If Relevanssi creates an empty excerpt for a post and there’s a user-set excerpt for the post, that excerpt is used.
No ellipsis is added to the post excerpt, if the post excerpt shows the whole post.
The relevanssi_post_title_before_tokenize filter now has a second parameter that contains the post object.
New filter: relevanssi_display_common_words can be used to disable the “25 most common words” listing on the settings page, if it’s too heavy to load.
Relevanssi was sanitizing taxonomy titles too aggressively. That is now toned down a bit.
Relevanssi now supports post_parent, post_parent__in and post_parent__not_in, though you have to set them in relevanssi_modify_wp_query filter for them to work.
Meta query support should now be perfect; there were some limitations with complicated meta queries before.

3.3.8

Fixed a bug that caused the results to change depending of the order of words in a multi-word search query.
Added product_categories and recent_products from WooCommerce to the list of blocked shortcodes.
There are improvements in excerpt-building and highlighting, especially when fuzzy search is enabled.
Fixed a possible (if quite unlikely) XSS vulnerability.
Improved search performance (thanks to MikeNGarrett).
Sometimes highlights in documents make the document content disappear. I don’t know why, but I’ve added a fix that should make the content visible (without the highlights) if a problem appears.

3.3.7.1

Fixed bbPress compatibility.

3.3.7

Fixed bbPress compatibility.

3.3.6

Relevanssi handles taxonomy terms in search better. The change requires a reindexing.
Fix in indexing: Relevanssi will now bypass the global $post when indexing. This should help with problems with the Cookie Law Info plugin, for example.
Tax query relation setting didn’t work properly. It is now fixed.
Word-based excerpt building sometimes created too short excerpts. That is now fixed.
Synonyms are now highlighted.
Phrase matching had issues where searching for a too common phrase crashed the search. That has been fixed.
LIKE operator didn’t work properly in meta_queries.
Problems with Avatar Upload plugin are fixed.
Offset errors with mb_stripos() shouldn’t happen anymore.
A small problem in taxonomy search MySQL fixed, also a small problem with AND operator in tax_queries.
New filter: relevanssi_post_to_index lets you access the post object before the post is indexed.
New filter: relevanssi_orderby lets you modify the $orderby value before Relevanssi sorts posts.
New filter: relevanssi_order lets you modify the $order value before Relevanssi sorts posts.
New filter: relevanssi_post_title_before_tokenize lets you modify post titles before indexing.
New filter: relevanssi_private_cap lets you adjust the capability setting for private posts in custom post types.
Deprecated use of like_escape has been fixed.

3.3.5

Fixed a bug where excluding posts would cause the search to fail.
Fixed a bug causing duplicate search results in WPML searches.
Increased plugin safety against hackers.
There was a bug in relevanssi_comment_content_to_index filter.
Some people had problems with the log entry timestamps. Fixed that.
New filter: relevanssi_prevent_default_request gives you more control over where Relevanssi prevents the default query from running.
New filter: relevanssi_private_cap lets you set the correct capability for finding private posts in custom post types.
The option to exclude categories and tags from search only worked for categories, not tags. Tags have been separated to a different option.

3.3.4

Couple of bug fixes.

3.3.3

OR fallback had problems.
Indexing sub pages didn’t work.
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.

3.3.2

Fixed a warning on search results page.

3.3.1

Fixed bugs related to the removal of the cache feature.

3.3

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.

3.2

Fixed a bug in the TablePress support.
Titles are put through the_title filter before indexing.
New filter: relevanssi_join can be used to join tables in the Relevanssi search MySQL queries. Thanks to Ninos Ego.
New filter: relevanssi_post_content can be used to modify post content before any Relevanssi processing.
New filter: relevanssi_post_content_before_tokenize can be used to modify post content just before it’s tokenized.
New filter: relevanssi_indexing_values can be used to modify what Relevanssi stores in the index.
New filter: relevanssi_default_meta_query_relation can be used to change the default meta query relation (default value is “AND”).
When using a meta_query, relation can be set to OR now.
Phrases are now matched to excerpts.
Number of queries Relevanssi generates is much, much lower.
New filter: relevanssi_didyoumean_url lets you modify the URL generated by the did you mean feature.
Better set of Russian stopwords.
Relevanssi now highlights search query synonyms as well in documents.

3.1.9

Fix to make Relevanssi compatible with WordPress 3.7.
Fixed a mistyped database table name.
Relevanssi disables responsive-flipbook shortcode in indexing; it was causing problems.
Fixed a problem with an author dropdown with no author selected.

3.1.8

Category restriction and exclusion and couple of other category-related settings didn’t work properly.
Support for Polylang broke the support for WPML. That is now fixed.
One deprecated $wpdb->escape() was still left; it’s gone now.
Shortcode layerslider was causing problems with Relevanssi; Relevanssi now disables it before building excerpts.
Relevanssi won’t break BBPress search anymore.
If Relevanssi Premium is installed, deleting Relevanssi will not remove the databases and the options.

3.1.7

New filter: relevanssi_comment_content_to_index lets you modify comment content before it’s indexed by Relevanssi (to index comment meta, for example).
Facetious support: if post_type is set to -1, Relevanssi will not hang up on it.
Numerical search terms work better now.
Excerpt-building had issues, which are now fixed.
Punctuation removal now replaces with a space.
“starrater” short code from GD Star Rating is now disabled in indexing.
Punctuation removal now replaces invisible spaces with a normal space.
Division by zero error caused by 0 in posts_per_page is now prevented, and -1 value for posts_per_page handled better.
Relevanssi doesn’t apply get_the_excerpt filters to excerpts it builds any more.
New filter: relevanssi_excerpt lets you modify the excerpts Relevanssi creates.
Relevanssi now suspends WP post cache while indexing, making indexing a lot more efficient. Thanks to Julien Mession for this one.
Deprecated function errors in 3.6 removed.
When search included user profiles or taxonomy terms, Relevanssi would generate lots of MySQL errors. Not anymore.
New filter: relevanssi_valid_status lets you modify the post statuses Relevanssi indexes.
New filter: relevanssi_index_taxonomies_args lets you modify the arguments passed to get_terms() when indexing taxonomies (for example to set ‘hide_empty’ to false).
Searching by taxonomy ID could confuse two taxonomies with the same term_id. The search is now checking the taxonomy as well to see it’s correct.
Basic support for Polylang plugin.
Russian and Italian stopwords are now included, thanks to Flector and Valerio Vendrame.
Small fix in the way user meta fields are handled.

3.1.6

DEACTIVATE AND ACTIVATE THE PLUGIN AFTER YOU UPDATE.
Fuzzy searches are now a lot more efficient; they were a huge resource hog before.
Fixed a possible MySQL injection attack.
Fixed MySQL errors from empty meta queries.
Sort order (orderby and order variables) are now read from query variables instead of global variables.
Relevanssi will not choke on bad values of orderby anymore.
Limit searches is improved: when using AND search it is less likely to miss results.
Phrase recognition read the whole post content (which it didn’t need) from database, causing memory issues in some cases. Fixed that.
Highlighting was broken, and should work much better now.

3.1.5

OR fallback didn’t actually fall back to OR, but instead got stuck in an endless loop of AND searches.
Meta queries didn’t work without a key; now they work with just meta_value or meta_value_num.
Meta queries had problems with meta_value being set to null.
Relevanssi now supports category__and. By default this sets include_children to false.
When querying by slug, the term taxonomy is also taken into consideration, fixing problems when same slug appears in different taxonomies.
Author search didn’t work.
Fixed an error message caused by all-number synonyms starting with zero, like 02.
Synonyms are now case-insensitive.
New filter: relevanssi_default_tax_query_relation can be used to change the default tax query relation from OR to AND.
Fixed undefined variable errors when doing an OR fallback.
New filter: relevanssi_bots_to_not_log makes it possible to block bots from logs. The format matches what other plugins, ie. WP-Useronline, use for bot blocking, so you can share block lists.
New filter: relevanssi_admin_search_ok gives you more control when Relevanssi overrides the default WP search in admin, useful for fixing P2P_Box AJAX search.
Ordering search results by title or date in admin search works now.
Modified the way the highlights work; now highlighting words with apostrophes should produce more meaningful results.
Highlighting should not highlight anything between & and ; or in or tags, thus solving some of the problems related to highlights. Reports of how well this works are welcome.
On-post highlighting now only highlights content in the loop, so menu texts and other off-the-loop stuff should not get highlights anymore.
New action hook: relevanssi_pre_indexing_query can be used to “SET OPTION SQL_BIG_SELECTS=1” if needed.
Major indexing problems caused by shortcodes changing the post ID during the indexing of posts are now fixed.
Relevanssi was being called twice when a post was saved, on save_post and wp_insert_post. I removed the hook on save_post.
Unsuccessful searches are now ordered by count, like the successful queries are.

3.1.4

Choosing which taxonomies to index is now done with an easy-to-use checkbox list.
Support for WP Table Reloaded and TablePress. Tables created with these plugins will now be expanded and the content indexed by Relevanssi.
New filter: relevanssi_index_comments_exclude can be used to exclude comments from indexing. The filter gets the post ID as a parameter, so you can prevent comments of particular posts being indexed, yet index those posts.
Relevanssi now adds spaces between tags when creating excerpts to make neater excerpts from tables and other similar situations.
Relevanssi now indexes unattached attachments, if you choose to index attachments.
Fixed the problems with Twenty Ten and Twenty Eleven themes better.
$match->tag now contains the number of tag hits.
Relevanssi now adds relevance score to posts before passing them to relevanssi_hits_filter. You can find it in $post->relevance_score.
Tags in breakdowns always showed 0, even though tags were indexed and searched correctly. That’s now fixed.

3.1.3

AND search did not work in all cases.
Posts couldn’t be found by category name. Fixed that.

3.1.2

Exclude category option was broken. Fixed that.
Searching for a non-existing category ID caused an error. Fixed that.
Occasional blank screens of death occurred when multibyte string operations weren’t installed. That should not happen anymore.
Fallback to OR search was a bit broken.

3.1.1

Small fix to prevent database errors.
Small fix to prevent disappearing excerpts.

3.1

Fixed the uninstalling instructions.
Fixes a problem with Twenty Ten and Twenty Eleven themes that caused doubled “Continue Reading” links.
Fixed a notice about undefined variable on plugin update pages.
Small bug fixes on search to remove warning notices.
New filter: relevanssi_index_custom_fields can be used to modify the list of custom fields to index.
Deleting menus caused a warning. That is now fixed.
Relevanssi has an option to disable IP logging (which is actually illegal in some countries). Thanks to Stefan Eufinger.
Searching in subcategories worked sometimes, but not always. Thanks to Faebu.
The “Limit searches” option didn’t work too well in the case of strong weightings, as it didn’t take note of any weights. Now it works better.
Added a note about disabling custom excerpts when they are not needed – they can slow down the search quite a bit.
New filter: relevanssi_options_capability can be used to modify the capability required to see the options page (default is manage_options).
Fixed the way IDF is calculated to account some extreme cases with small databases.
New filter: relevanssi_index_custom_fields gives added control over which custom fields are indexed.
Fixed filter: relevanssi_pre_excerpt_content wasn’t working properly.
Relevanssi now supports tax_query, for most part. You can query multiple taxonomies, use relation AND and OR, use operators AND, IN and NOT IN and choose include_children (which defaults to true). Old taxonomy and term still work, but I recommend using tax_query for the level of control it offers.
Relevanssi now works better with category restrictions. The extra cats query variable is no longer necessary, Relevanssi can now read multiple categories from cat. You can also use category__and, category__in and category__not_in.
Same goes with tags: tags is now longer necessary. Relevanssi has full support for tag, tag_id, tag__and, tag__in, tag__not_in, tag_slug__and, tag_slug__in and tag_slug__not_in. For tag, both term1+term2 and term1,term2 is supported.
Relevanssi now supports author_name and negative values for author.
Relevanssi now supports offset query variable.
Relevanssi now supports meta_query. You can use all comparisons (also EXISTS and NOT EXISTS, even if you don’t have WP 3.5). You can also use the older meta_key and meta_value query variables, including all the comparisons. I have not tested all possible meta_query constructions, so bug reports of things that don’t work as expected are welcome.
New index on the database makes some database operations faster.
Removed a bug that prevents one-character words from being indexed in titles, despite the minimum word length setting.
Removed a warning when searching for nothing.
Fixes a warning about $wpdb->prepare() caused by a change in WordPress 3.5.

3.0.5

AFTER UPGRADING FROM 2.x: Make sure you deactivate and reactivate Relevanssi in order to make the database changes happen.
Fixed a major bug that caused the searches to fail when “Limit searches” was enabled, but “Limit” was not defined.
Modified relevanssi_remove_punct() to replace curly apostrophes and quotes with spaces instead of removing them, to make the index more consistent (regular apostrophes were replaced with spaces). Reindexing the database is a good idea.
Fixed some misleading text on the options page.

3.0.4

AFTER UPGRADING FROM 2.x: Make sure you deactivate and reactivate Relevanssi in order to make the database changes happen.
Fixed another problem with the Jetpack Contact Form.
Fixed an error message caused by searching for numbers.
Phrases are now also recognized in drafts and attachments.
You can now set post_types to ‘any’.

3.0.3

AFTER UPGRADING FROM 2.x: Make sure you deactivate and reactivate Relevanssi in order to make the database changes happen.
Fixed a bug that made custom taxonomy term searches fail.
New filter: relevanssi_user_searches_capability lets you modify the minimum capability required to see the User searches page.

3.0.2

AFTER UPGRADING FROM 2.x: Make sure you deactivate and reactivate Relevanssi in order to make the database changes happen.
Fixed the “Cannot use a scalar value as an array” bug in indexing.
Role-Scoper users: in order to make Relevanssi work with Role-Scoper, replace the Relevanssi helper file in Role-Scoper with this file.
Removed an error message about set_time_limit() under safe_mode.
Jetpack Contact Form shortcode caused problems when indexing. Relevanssi will now simply remove the shortcode before indexing.
Fixed errors caused by / characters in highlighting.

3.0.1

AFTER UPGRADING FROM 2.x: Make sure you deactivate and reactivate Relevanssi in order to make the database changes happen.
Fixed lots of problems in logging searches.
Added an alert when user hasn’t selected any post types to index (and default values).
Custom field setting ‘visible’ works now.
Searching by category title works now, and you can adjust the category weight in the settings.

3.0

AFTER UPGRADING FROM 2.x: Make sure you deactivate and reactivate Relevanssi in order to make the database changes happen.
WORD OF WARNING: This is a major update, with lots of changes as you can see, and since I couldn’t find any beta testers to help test it out, consider this a beta release, with bugs probable.
The database has been updated to match the more advanced structure in Relevanssi Premium. This requires a re-indexing of the database.
The indexing process is more efficient now.
Relevanssi now includes a throttle feature, which makes the searches more efficient.
Relevanssi now disables the default WP search.
The custom field search hack using cat set to “custom” doesn’t work any more. If you wish to filter by custom field, you need Relevanssi Premium, which does it better anyway.
Relevanssi can handle certain whitespace characters better in indexing.
Apostrophes are now replaced with whitespace instead of being removed.
Relevanssi now shows correct number of results when posts_per_page is set to -1.
Fuzzy search didn’t always activate when it should, if all found posts are private posts that can’t be shown to user.
Tab characters in excerpts are handled better now.
Relevanssi search logs will now store user ID’s and IP addresses for each query.
You can now use user logins as well as numeric ID’s to stop user from being logged.
Attachments are now handled better. I’d still like to hear any complaints about attachments.
Relevanssi now updates index for posts added with wp_update_post() function. (Thanks to Simon Blackbourn)
Searching for pages in admin didn’t work properly. Fixed that.
Fixed warnings for undefined variables.
Relevanssi won’t mess media library searches any more.
Search terms are no longer highlighted in titles on post pages. That caused too many problems.
New collation rules to MySQL databases will make sure that word pairs like “pode” and “pôde” will not be considered duplicates in the stopword database.
You can now set the “Custom fields to index” to “all” to index all custom fields and “visible” to index all visible custom fields (but not the ones with names starting with an underscore).
Plugin now works properly without multibyte string functions.
You can now choose to allow HTML tags in excerpts.
New filter: relevanssi_modify_wp_query lets you modify $wp_query before it is passed to Relevanssi.
New filter: relevanssi_search_ok lets you adjust when search is enabled.
New filter: relevanssi_pre_excerpt_content lets you adjust post content before excerpt creation.
New filter: relevanssi_excerpt_content lets you adjust post content before excerpt creation, but after the_content.
New filter: relevanssi_ellipsis lets you change the default ‘…’ in excerpts to something else.
New filter: relevanssi_do_not_index is given a post ID and expects a boolean in return: should this post be indexed or not?
New filter: relevanssi_match lets you meddle with the matching engine.
New filter: relevanssi_results filters the result set from the search.
New filter: relevanssi_content_to_index let’s you add whatever content you wish to posts before they are indexed.
New filter: relevanssi_didyoumean_query let’s you modify the query for Did you mean? queries
Changed filter: relevanssi_post_ok has different arguments, see source code for details.
New shortcode: use shortcode noindex to wrap parts of posts you want to keep from the index.
And a bunch of other changes.

2.9.14

Relevanssi will now index pending and future posts. These posts are only shown in the admin search.

2.9.13

Stripping shortcodes from excerpts didn’t work properly. Should work now.
Fixed a mistake in the FAQ: correct post date parameter is post_date, not date.
New filter relevanssi_results added. This filter will process an array with (post->ID => document weight) pairs.
Private and draft posts were deleted from the index when they were edited. This bug has been fixed. (Thanks to comprock.)
When continuing indexing, Relevanssi now tells if there’s more to index. (Thanks to mrose17.)
Fixed problems with searching attachments. Indexing attachments still has some problems. When you build the index, attachments are indexed properly.
Improved WPML support.
The relevanssi_index_doc() function has a new parameter that allows you to bypass global $post and force the function to index the document given as a parameter (see 2.9.13 release notes at Relevanssi.com for more details).

2.9.12

Scheduled cache truncate wasn’t scheduled properly. It is now.
Added support for ‘author’ query variable.
Fixed a bug with indexing custom post types.

2.9.11

Plugin now works properly without multibyte string functions.
Fixed s2member support for s2member versions 110912 and above. (Thanks to Jason Caldwell.)
Added support for ‘tag’ query variable.

2.9.10

AND search failed, when search query included terms that are shorter than the minimum word length.
Improved s2member support.
Fixed errors about deprecated ereg_replace.
Small fix to Did you mean suggestions.

2.9.9

Removed warnings about undefined functions and missing $wpdb.
Fixed a bug that removed ‘à’ from search terms.
Phrases are recognized from custom field searches.

2.9.8

Support for s2member membership plugin. Search won’t show posts that the current user isn’t allowed to see.
New filter relevanssi_post_ok can be used to add support for other membership plugins.
Post meta fields that contain arrays are now indexed properly, expanding all the arrays.

2.9.7

Fixed a bug that causes problems when paging search results.
Taxonomy term restrictions didn’t work most of the time.
the_content filters didn’t run on excerpts.
Style data and other extra elements created by short codes are now stripped.

2.9.6

Fixed a problem causing “Attempt to modify property of non-object” errors.
Fixed a warning message.

2.9.5

Searching for private posts caused an error message.

2.9.4

Relevanssi should now be much lighter on server.
Post date selection didn’t work properly. Fixed that.
Stopwords can be exported.
Restricting indexing on custom post types works better.
Minimum word length is properly enforced in indexing.
Punctuation removal is more efficient.
Fixed a MySQL error that was triggered by a media upload.
Fixed a bug that caused an error when quick editing a post.

2.9.3

A call to a non-existing function in 2.9.2 made all sorts of mess. This release fixes all problems with broken loops. I’m sorry about the bug.

2.9.2

It’s now possible to adjust the number of search results per page. See Changing posts_per_page for instructions.
Somebody reported revisions appearing in the search results. Added an extra check to prevent that.
Improved the indexing procedure to prevent MySQL errors from appearing and to streamline the process.
Improved the way custom post types can be handled in indexing.
Improved the method of removing nested highlights.

2.9.1

It is now possible to change the default result order from relevance to post date.
Fixed a bug that caused wrong $post object to be set in indexing.
Added a new hook relevanssi_excerpt_content; see Knowledge Base for details.

2.9

Fixed a bug that caused Cyrillic searches in the log to get corrupted.
Punctuation removal function is now triggered with a filter call and can thus be replaced.
Google Adsense caused double hits to the user search logs. That’s now fixed thanks to Justin Klein.
User search log is available to user with edit_post capabilities (editor role). Thanks to John Blackbourn.
A proper database collation is now set. Thanks to John Blackbourn.
UI looks better. Thanks to John Blackbourn.
Lots of small fixes here and there.

2.8.2

The order parameter was case sensitive. It isn’t anymore.
WordPress didn’t support searching for multiple categories with the cat query variable. There’s now new cats which can take multiple categories.
Similar to cats vs cat, you can use post_types to restrict the search to multiple post types.

2.8.1

Fixed two small mistakes that caused error notices.
Custom post types, particularly those created by More Types plugin, were causing problems.

2.8

There’s now a way to truncate the cache (sorry it took so long). Expired cache data is now automatically removed from the database every day. There’s also an option to clear the caches.
Highlights didn’t work properly with non-ASCII alphabets. Now there’s an option to make them work.
Title highlight option now affects external search term highlights as well.
There were some bugs on the options page.

2.7.5

There was a bug that caused shortcodes to fail in 2.7.4. That’s fixed now.
Category search will now include subcategories as well, both when including and excluding.

2.7.4

Improved the fallback to fuzzy search if no hits are found with regular search.
AND searches sometimes failed to work properly, causing unnecessary fallback to OR search. Fixed.
When using WPML, it’s now possible to choose if the searches are limited to current language.
Adding stopwords from the list of 25 common words didn’t work. It works now.
The instructions to add a category dropdown to search form weren’t quite correct. They are now.
Small fix that makes shortcodes in posts more compatible with Relevanssi.

2.7.3

IMPORTANT SECURITY UPDATE: Earlier versions of Relevanssi have a cross-site scripting (XSS) vulnerability. Please install this update as soon as possible.
Added instructions of doing a category dropdown in the search form in the FAQ.

2.7.2

A silly typo caused the caching not to work. That’s fixed now.
A new filter: relevanssi_didyoumean_query lets you modify the query used for ‘Did you mean?’ searches.

2.7.1

Thanks to a bug in the code, the WPML support didn’t work. It’s fixed now.

2.7

Caching search results is possible. If you have lots of repeated queries, caching will provide extra speed and less wear on server.
Multilanguage plugin WPML is now supported. If WPML is active, Relevanssi will automatically restrict search results to current language.
New filter: relevanssi_search_filter lets you adjust search query variables. See source code for further details. Thanks to Sam Hotchkiss.
Got a report of synonyms not working; hopefully fixed it now.
It is now possible to set the minimum word length to index. Default is now 3 instead of 2.
You can now add several stopwords at one go and remove all stopwords.
Author search didn’t work properly. It works now.
Search result highlighting functions properly now, there might’ve been some problems with it.

2.6

New setting allows user to define how exclude_from_search is handled. It’s now possible to exclude a custom post type from general searches and search for it specifically by defining post_type.
New filter: relevanssi_hits_filter lets you process hits found by Relevanssi. See FAQ.

2.5.6

Attachments are no longer automatically indexed; there’s an option for it now.
You can now exclude custom post types from index.
When AND search fails, it falls back to OR search. It’s now possible to disable this fallback.

2.5.5

The stopword management created empty stopwords. It won’t anymore.
Faulty HTML code in the admin page has been fixed.
Indexing shortcodes that need the global $post context is now possible.
Relevanssi is now aware of attachments and manages post_status of “inherit”.
These fixes were provided by Warren Tape, thanks!

2.5.4

Small bugfix relating to post types.
Added stopword management tools: way to remove and add stopwords.
Custom excerpts can now be created from post excerpts as well, if those are indexed.
Added answers to some frequently asked questions to the documentation.

2.5.3

Very small bugfix fixing the error on line 1192.

2.5.2

Fixed a bug about mysql_real_escape_string() expecting a string.
Added documentation about compatibility issues.

2.5.1

Option to highlight search terms in comment text as well.
Fixed a small problem in highlighting search terms.

2.5

Better support for other search plugins like Dave’s WordPress Live Search.
New User searches screen that shows more data about user searches.
Search logs can now be emptied.
Custom fields weren’t indexed on updated posts. That is now fixed.
Once again improved the highlighting: now the highlighting will look for word boundaries and won’t highlight terms inside words.
Relevanssi query engine can now be accessed directly, making all sorts of advanced hacking easier. See FAQ.

2.4.1

Fixed a problem where search term highlighting was changing terms to lowercase.
Fixed a problem with highlighting breaking stuff in shortcodes.
Made some changes to the admin interface – there’s more to come here, as the admin page is a bit of a mess right now.

2.4

Highlighting post content won’t highlight inside HTML tags anymore.
Soft hyphens inside words are now removed in indexing. They still confuse the highlighting.
Matching engine is now able to match category titles that contain apostrophes.

2.3.3.1

Suppressed the error messages on the correct mb_strpos() function call. If you still get mb_strpos() errors, update.
Added a FAQ note on getting the number of search results found.

2.3.3

Suppressed notices on one mb_strpos() call.
Added a search variable “by_date” to filter search results, see FAQ for details.

2.3.2

Fixed a serious bug related to taxonomy term searches that could cause strange search results. Thanks to Charles St-Pierre for finding and killing the bug.
Spanish stopwords are now included (thanks to Miguel Mariano).

2.3.1

I fixed the highlighting logic a bit, the highlighting didn’t work properly before.

2.3

New highlighting option: HTML5 mark tag. Thanks to Jeff Byrnes.
Relevanssi can now highlight search term hits in the posts user views from search. Highlighting for search term hits from external searches will be added later.
It is now possible to add custom filtering to search results, see FAQ for details. Thanks to Charles St-Pierre.
Removed search result highlighting from admin search, where it wasn’t very useful.

2.2

Relevanssi used to index navigation menu items. It won’t, anymore.
Translation and stopwords in Brazilian Portuguese added, thanks to Pedro Padron.

2.1.9

No changes, I’m just trying to resurrect the broken Relevanssi plugin page.

2.1.8

Including the popular microtime_float function caused conflicts with several other plugins (whose authors are just as sloppy as I am!). Fixed that.

2.1.7

The index categories option wasn’t saved properly. Now it is.
Fixed the %terms% breakdown option to show correct counts and added %total% to show total hit count.
Phrases are now matched also in post titles and category titles (before they were only matched against post content).
Post excerpts can now be indexed and searched. I would appreciate feedback from people who use this feature: do you use the excerpts in search results? If you use custom snippets created by Relevanssi, what you want them to display?
Set the constant TIMER to true to enable timing of the search process for debugging reasons.

2.1.6

Title highlighting caused an error. That is now fixed. I also streamlined the highlighting code a bit.

2.1.5

You can now enter synonyms, expanding queries with synonyms when doing an OR search. This is useful to expand acronyms and abbreviations, for example.
When doing a phrase search, highlighting will only highlight phrase hits.
New breakdown variable %terms% will list hits by term.
Some users reported error messages about unexpected T_OBJECT_OPERATOR. Those shouldn’t happen, please let me know if they still do.
Highlighting will now highlight only complete words.

2.1.4

Fixed a small bug that could cause all queries by anonymous users to go unlogged.

2.1.3

OR operator makes a comeback! The default operator is now an option, and if you choose AND and search gets no results, an OR search is also run.
You can now give a list of user ids – any searches by those users will not be logged. List your admin user id, so your test searches won’t clutter the log.

2.1.2

Removing punctuation didn’t work properly, making phrase search impossible. I’d thought I’d fix it, but for some reason I made a mistake and the fix didn’t appear in the released versions.
Search has now an implicit AND operator, which means that every search term must appear in all result documents. Please let me know if you’d prefer an implicit OR operator, like Relevanssi had before.
Relevanssi options page now shows the amount of indexed documents, making troubleshooting indexing easier.

2.1.1

“Did you mean” suggestions now work in blogs that are not in root directory.
Early 2.1 downloads had faulty encodings. Update to make sure you’ve got a good file.

2.1

An experimental “Did you mean” suggestion feature. Feedback is most welcome.
Added a short code to facilitate adding links to search results.
Fixed a small bug that in some cases caused MySQL errors.

2.0.3

Fixed problems relating to the orderby parameter.

2.0.2

Small bug fix: with private posts, sometimes correct amount of posts weren’t displayed.

2.0.1

Exclude posts/pages option wasn’t saved on the options page. It works now.
2.0 included an unnecessary function that broke Relevanssi in WP 2.8.5. Fixed that.

2.0

Post authors can now be indexed and searched. Author are indexed by their display name.
In search results, $post->relevance_score variable will now contain the score of the search result.
Comment authors are now included in the index, if comments are indexed.
Search results can be sorted by any $post field and in any order, in addition of sorting them by relevancy.
Private posts are indexed and displayed to the users capable of seeing them. This uses Role-Scoper plugin, if it’s available, otherwise it goes by WordPress capabilities.
Searches can be restricted with a taxonomy term (see FAQ for details).

1.9

Excerpts are now better and will contain more search terms and not just the first hit.
Fixed an error relating to shortcodes in excerpts.
If comments are indexed, custom excerpts will show text from comments as well as post content.
Custom post type posts are now indexed as they are edited. That didn’t work before.
Cleaned out more error notices.

1.8.1

Sometimes empty ghost entries would appear in search results. No more.
Added support for the WordPress’ post_type argument to restrict search results to single post type.
Relevanssi will now check for the presence of multibyte string functions and warn if they’re missing.
The category indexing option checkbox didn’t work. It’s now fixed.
Small fix in the way punctuation is removed.
Added a new indexing option to index all public post types.

1.8

Fixed lots of error notices that popped up when E_NOTICE was on. Sorry about those.
Custom post types can now be indexed if wanted. Default behaviour is to index all post types (posts, pages and custom types).
Custom taxonomies can also be indexed in addition to standard post tags. Default behaviour is to index nothing. If somebody knows a way to list all custom taxonomies, that information would be appreciated.

1.7.3

Small bug fix: code that created database indexes was broken. Say “ALTER TABLE wp_relevanssi ADD INDEX (doc)” and “ALTER TABLE wp_relevanssi ADD INDEX (term)” to your MySQL db to fix this for an existing installation.

1.7.2

Small bug fix: public posts that are changed to private are now removed from index (password protected posts remain in index).
An Italian translation is now included (thanks to Alessandro Fiorotto).

1.7.1

Small fix: the hidden variable cat now accepts negative category and tag ids. Negative categories and tags are excluded in search. Mixing inclusion and exclusion is possible.

1.7

Major bug fix: Relevanssi doesn’t kill other post loops on the search result page anymore. Please let me know if Relevanssi feels too slow after the update.
Post categories can now be indexed.

1.6

Relevanssi is now able to expand shortcodes before indexing to include shortcode content to the index.
Fixed a bug related to indexing, where tag stripping didn’t work quite as expected.

1.5.3

Added a way to uninstall the plugin.
A French translation is now included (thanks to Jean-Michel Meyer).

1.5.2

Fixed a small typo in the code, tag and comment hit count didn’t work in the breakdown. If you don’t use the breakdown feature, updating is not necessary.

1.5.1

User interface update, small changes to make the plugin easier to use.
Fixed a small bug that sometimes causes “Empty haystack” warnings.

1.5

Comments can now be indexed and searched (thanks to Cristian Damm).
Tags can also be indexed (thanks to Cristian Damm).
Search term hits in the titles can be highlighted in search results (thanks to Cristian Damm).
When using custom excerpts, it’s possible to add extra information on where the hits were made.
Fuzzy matching is now user-adjustable.
UTF-8 support is now better (thanks to Marcus Dalgren).

1.4.4

Added an option to exclude posts or pages from search results. This feature was requested and provided by Cristian Damm.

1.4.3

Indexing of custom fields is now possible. Just add a list of custom field names you want to include in the index on the settings page and re-index.

1.4.2

Users can search for specific phrases by wrapping the phase with “quotes”.
Fixed a bug that caused broken HTML in some cases of highlighted search results (search term matches in highlighting HTML tags were being highlighted).
Improved punctuation removal. This change requires reindexing the whole database.

1.4.1

Fixed a bug that caused empty search snippets when using word-based snippets.
Improved support for WP 2.5.
Added an option to exclude categories and tags from search results.
Added an option to index only posts or pages.
Added French stopwords.

1.4

Added an option to restrict searches to certain categories or tags, either by plugin option or hidden input field in the search form.
The contents of <script> and other such tags are now removed from excerpts.
When indexing, HTML tags and [shortcodes] are removed.
Digits are no longer removed from terms. Re-index database to get them indexed.
Wrapped the output of relevanssi_the_excerpt() in

p> tags.
* Stopwords are no longer removed from search queries.
* Search result snippet length can now be determined in characters or whole words.

1.3.3

Small bug fixes, removed the error message caused by a query that is all stop words.
Content and excerpt filters are now applied to excerpts created by Relevanssi.
Default highlight CSS class has a unique name, search-results was already used by WordPress.

1.3.2

Quicktags are now stripped from custom-created excerpts.
Added a function relevanssi_the_excerpt(), which prints out the excerpt without triggering wp_trim_excerpt() filters.

1.3.1

Another bug fix release.

1.3

New query logging feature. Any feedback on query log display features would be welcome: what information you want to see?
Added a CSS class option for search term highlighting.
Fixed a bug in the search result excerpt generation code that caused endless loops with certain search terms.

1.2

Added new features to display custom search result snippets and highlight the search terms in the results.

1.1.3

Fixed a small bug, made internationalization possible (translations are welcome!).

1.1.2

English stopword file had a problem, which is now fixed.

1.1.1

Fixed a stupid bug introduced in the previous update. Remember always to test your code before sending files to repository!

1.1

Fixes the problem with pages in search results.

1.0

First published version.