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…
…think it has). Since that too is a visible field, Relevanssi indexes it and uses it for excerpts. Thus the layout names appear in excerpts. The solution to this problem is to remove the root field, flexible_content, from the Relevanssi index and excerpts. That is a straightforward thing to do…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……with a filter function: add_filter( ‘relevanssi_index_custom_fields’, ‘rlv_remove_unwanted’ ); function rlv_remove_unwanted( $fields ) { $unwanted_fields[] = ‘flexible_content’; return array_diff( $fields, $unwanted_fields ); } Add this function to your site and rebuild the index. Now the root field is no longer indexed or used in excerpts. Another approach is to stop using…
It’s been a while since the previous version, and the list of features and bug fixes in this version has grown long. This version includes several interesting new features, both for free and Premium. Free version users get access to better debugging tools. There’s now a Debugging tab in the Relevanssi settings, which lets you…
…include numbers. Relevanssi init is now moved from priority 10 to priority 1 on the init hook to avoid problems with missing TablePress compatibility. Major fixes Relevanssi didn’t index new comments when they were added; when a post was indexed or the whole index rebuilt, comment content was included. I…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……now supports date parameters. New feature: Both relevanssi_fuzzy_query and relevanssi_term_where now get the current search term as a parameter. New feature: New filter hook relevanssi_tabs can be used to adjust the tabs in Relevanssi settings page to add, modify or delete the tabs. (Premium) Major fix: The post_relevanssi_related action hook…
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……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. New filter: relevanssi_user_add_data lets you add…