Simple bug fix release. 1.7.8 had some overeager optimization attempts that failed and caused some searches simply not work. I removed those and everything should work now.
Related Posts
Premium 2.12 / Free 4.10
This version started as a small update to 2.11 and 4.9, but then a customer request made me add a major enough feature to warrant a bigger version number update. The big new feature in this version...
Premium 2.26 / Free 4.23 release notes
This version includes bug fixes, small quality-of-life improvements, and a small security fix. In earlier versions, Relevanssi included password-protected posts in the search results. This can be used...
Premium 1.8
Relevanssi Premium 1.8 is finally out. It's been a while from the previous version, and the list of fixes in this version is longer than it has ever been. Then again, that's part of the reason why it ...
Premium 1.14
1.14 is a major release and includes lots of bugfixes and some new features. Here's the full list of features: Tokenizer was using strlen() and not mb_strlen(), so word lengths were not calculated ...
Premium 1.16.1 / Free 3.6.1
I was told today that there is a security vulnerability in Relevanssi. It is possible to set the post type and taxonomy weights to values that are not numeric, and those values will be inserted into S...
Premium 1.5.7
Small fixes. I got some bug reports and feature requests, so I implemented them: Added default values to the database columns, this could cause some problems. Indexing could cause problems, beca...
Great plugin, but I have got a problem. The update core page displays all the time, that relevanssi is not up to date.. How can I fix this problem, because it’s a litte bit annoying.. 🙂
Yes – this is mentioned on the support page and in every email update I’ve sent to users. If it bothers you, remove the API key from the settings page.
I’m hoping to get this fixed in the next version.
k so I will wait to the next version 🙂