This might not have worked before, but WordPress’s meta queries now support the relation parameter. To complete what @s_ha_dum was looking to do, simply add the relation parameter (as OR) and add a second meta query for NOT EXISTS. Example: function searchExcludeOldMatches( $query ) { //if we’re on the admin panel, or it’s a search, … Read more
There are a few concerns here in the registration of your custom taxonomy as from the comments on your OP, this is not your code, but a client’s code. Still, taxonomy and custom post type names should never contain hyphens, just underscores to separate words there are non valid arguments used like exclude_from_search and has_archive … Read more
It looks like this section: AND (wptom_posts.post_status=”publish” OR wptom_posts.post_author = 1 AND wptom_posts.post_status=”private”) is not tied in at all to the two different query conditions… Perhaps the original code should be three conditions for part 1: array( ‘relation’ => ‘AND’, array( ‘taxonomy’ => ‘category’, ‘field’ => ‘slug’, ‘operator’ => ‘IN’), array( ‘taxonomy’ => ‘post_tag’, ‘field’ … Read more
pre_get_posts is innapropriate for this use, instead you should use the template_redirect filter, e.g. add_action( ‘template_redirect’, funnction() { if ( ! is_user_logged_in() && is_page( 123 ) ) { wp_safe_redirect( home_url( ‘/sample-page’ ) ); exit; } } );
Did you try this one? <?php $blogpost = new WP_Query(array( ‘post_type’ => ‘post’, ‘posts_per_page’ => 6 )); ?> <?php while($blogpost->have_posts()) : $blogpost->the_post(); ?> // Writhe your Blog article Here. <?php endwhile; ?>
Changing a query for the page post type via pre_get_posts is a bit tricky, and maybe not worth the potential issues involved. If you inspect the generated SQL, it’s looking for your requested pagename in the question post type, which is why you get the 404. The solution is to delete the page, so WordPress … Read more
Never forget that there’re actually two filters // Add additional query args that are allowed by the API by default pre_get_posts // Modify the query herself posts_clauses // Inspect the resulting string – test this one in for e.g. phpMyAdmin posts_request So everything you can achieve using the pre_get_posts filter should be done there. The … Read more
Thanks to s_ha_dum for the tip. I managed to solve it by setting the offset parameter in the special case of 2nd page onwards for the front page as follows: function limit_posts_per_home_page() { $paged = (get_query_var(‘paged’)) ? get_query_var(‘paged’) : 1; $first_page_limit = 5; $limit = get_option(‘posts_per_page’); if (is_front_page()) { if ($paged == 1) { $limit … Read more
I’m not sure at first glance why this is only working on your home page and not your archive pages, but there are a few things wrong with the way this function is written. So, I’ve rewritten it for you below – using this instead might solve the problem if it was introducing an esoteric … Read more
I’d make 2 queries. This would look something like this : function add_role_filter_to_posts_administration(){ //execute only on the ‘post’ content type global $post_type; if($post_type == ‘post’){ $user_role=””; // Get all user roles $user_roles = array(); foreach ( get_editable_roles() as $key => $values ) : $user_roles[ $key ] = $values[‘name’]; endforeach; // Set a selected user role … Read more