On sites where ACF fields are used a lot, with Flexible Content and Repeater fields, it may be difficult to make Relevanssi only index the relevant ACF fields. One way to deal with problem is to set Relevanssi to index “visible” custom fields and then restrict the indexed fields by field type. Add this function…
With Advanced Custom Fields, sometimes Relevanssi picks up custom field names to include in the excerpts. This problem happens when you set Relevanssi to index all visible custom fields and have Flexible Content fields. Let’s assume there’s a Flexible Content field with the name flexible_content. It has a layout named field_layout, and in that layout,…
…(but remember to remove it when the next version is released). Searching for words that end in “s” can cause slightly broken highlighting. The easiest fix for this is to enable the “Expand highlights to cover full words” setting. The “Post exclusion” setting does not work correctly at the moment….…excluded from the index. There’s a new option, “Expand highlights”. Enabling it makes Relevanssi expand partial-word highlights to cover the full word. This is useful when doing partial matching and when using a stemmer. (Premium) Relevanssi can now generate excerpts that show multiple snippets from the post. You can adjust……content to eg. remove unwanted sections. Changed behaviour The “Uncheck this for non-ASCII highlights” option has been removed. Highlights are now done in a slightly different way that should work in all cases, including for example Cyrillic text, thus this option is no longer necessary. (Premium) The index_pdfs WP CLI…
After the Summer break, Relevanssi is back with new versions, both to Premium and free. These are mostly small improvements, but when testing the new version, I discovered a bug in the comment indexing that has made Relevanssi not index comments when they are added. I’m not sure why this……hasn’t come up in tests before this. Relevanssi also now requires PHP 7. It should not be possible to update Relevanssi on sites that are still running PHP 5. If your site is running PHP 5, it’s badly irresponsible and you really, really should update the PHP version to something……is available from the WordPress plugin repository. You can get the Premium version from the Download page or with the automatic update. The download page shows two different versions of the plugin available. The basic version no longer includes tests or anything else you won’t need when actually using the…
Version 4.0.3 fixes problems in Relevanssi 4.0.2. The biggest issue is the indexing: version 4.0.2 always leaves some posts unindexed and requires the user to continue indexing. This version fixes that issue and other small issues. Relevanssi didn’t index all posts with one go. It does now. © and ® symbols caused problems in indexing;…
Version 2.0.3 is mostly maintenance, fixing bugs in previous versions. There have been some issues with the PDF indexing, some wrinkles we’re still ironing out. As a new feature, you can now have Relevanssi automatically read the contents of new PDF files – that wasn’t possible before. This setting is disabled by default, as it…
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 SQL queries, making SQL injection possible. However, it requires either admin access to the WordPress dashboard or direct access…
Hot on the heels of Premium 1.10.1, there’s Relevanssi 3.1, bringing most of the new features to the free version. 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…
The beta testers had no complaints, so here goes: Relevanssi Premium 1.10 and a ton of updates. Made some changes to how user profiles and taxonomy terms are handled. As a result, there should be less warning notices. For user profiles, you can now find the user id in $post->user_id and for taxonomies, the term…