Free 3.5.10

Version 3.5.9 caused a very nasty fatal parse error on some users. This version fixes that, and also several smaller, rare errors. The recent changes in Relevanssi made life complicated for FacetWP users; that is also fixed.

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.

Your account

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

Search

Popular Resources

Relevanssi breaks autoembeds on result pages

…If the search becomes too slow, look for the next approach. Use autoembed directly Using apply_filters( ‘the_content’, $content_with_embed ) to do the autoembeds is not the ideal way to approach this in the first place. It does get the job done, but may have unwanted side effects for example from…

Automatic redirects to category archives

…This will make sure your redirection settings are always up to date. To create the first redirects, you need to add this function to your site and then save a product category term. This does not remove redirects for non-existing categories, so that is something you need to maintain manually….

Utf8mb4 charset and index problems

If you use utf8mb4 charset, Relevanssi database table may be missing an index. That’s because part of the index includes…