Premium 1.13.1

1.13.1 is a quick bug-fix release following on the heels of 1.13. The main target is the user search bug, but I’ve added couple of other bug fixes and improvements. Unless you need the user search, updating is not mandatory.

Fixed a bug with numeric taxonomy terms.
Fixed a bug in user search.
API keys are now completely hidden on the Relevanssi settings page.
relevanssi_do_not_index hook is moved a bit, so that when updating posts, posts that are not indexed because of the hook are now removed from the index.
Pinning didn’t work if the post wasn’t otherwise found with the pinning term. Now pinning terms are also indexed to ensure that the posts can be found with them.

Your account

Not logged in. Log in to see your license details.

Search

Popular Resources

Visual Composer: Indexing headings

Relevanssi doesn’t by default index the headings in Visual Composer. The vcex_heading shortcode Visual Composer for the headings stores the…

Toolset Views

…you’d expect. Because of the way the Toolset Relevanssi compatibility is built, the query variables are not passed to Relevanssi from the search query like they are when Toolset is not involved. This may lead to confusion, when adding a query variable (for example &post_types=page) to the URL has no……effect on the results, even though you can tell for sure the search is powered by Relevanssi. The reason is simple: Relevanssi doesn’t see that query variable, because Toolset does not pass it to Relevanssi. Fortunately Toolset provides means to fix this. There’s a filter hook you can use to…

ThemeCo

ThemeCo themes use custom codes for dynamic content. Those are not usual shortcodes, and Relevanssi won’t expand them automatically. In…