Premium 1.5.1

A quick bug-fix, fixing problems with 1.5 and earlier problems uncovered by someone who wanted to use a particularly advanced feature and found out it doesn’t quite work. That happens, particularly with these advanced features that are really cool but which nobody really uses.

The result caching system didn’t work properly. It works now.
Limiting results with custom field key and value didn’t work properly: it matched the value to the whole field. Now it matches the value to any part of the custom field. That should make more sense.

Your account

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

Search

Popular Resources

MemberPress Downloads add-on

The Downloads add-on for MemberPress adds downloadable files to MemberPress. These files are stored outside the Media Library, so by…

OceanWP

…$post->blog_id ); } ?> <article id=”post-<?php the_ID(); ?>” <?php post_class(); ?>> <div class=”search-entry-inner clr”> <?php // Featured Image. get_template_part( ‘partials/search/thumbnail’ ); ?> <div class=”search-entry-content clr”> <?php // Title. get_template_part( ‘partials/search/header’ ); // Content. get_template_part( ‘partials/search/content’ ); // Read more button. get_template_part( ‘partials/search/readmore’ ); ?> </div><!– .search-entry-content –> </div><!– .search-entry-inner –>…

Metabox

…that can be used to create relationships between posts. If you are interested in indexing these related posts somehow, that does require extra steps since the relationships data is stored in a separate database table. Let’s assume we have books (custom post type book) and each book has a number……this function does is to check if the post is a book post. If it’s not, nothing is done. If it is a book, Relevanssi then fetches the connected authors from the wp_mb_relationships table based on the current post ID in the from column and the right relationship type (book-author)….