We can filter the posts_where clause of the generated SQL to also return the parent post/page and not just the parent’s children. Here we will set our own custom argument called wpse_include_parent, which, when set to true, will alter the generated SQL accordingly. All we need to do inside our posts_where filter is to check … Read more
Did you check what part of is_front_page() is causing it to return false? I could reproduce the problem by following the setup from the trac ticket. In my case inside this function the call to is_page() was returning false. I guess this is due to using $wp_query->set() for page_id and is_page is only causing the … Read more
I am updating my complete answer based on your clarification in the comment below. I hope this helps: <div class=”entry-content”> <h2>Documents written by this writer</h2> <?php /* * Query posts for a relationship value. * This method uses the meta_query LIKE to match the string “123” to the database value a:1:{i:0;s:3:”123″;} (serialized array) */ $documents … Read more
Yes, it is possible, but it is a bit of a pain. Looking at the codex page, only arguments of note are number and offset. We need these two to create our paginated pages. First, we set the $paged parameter, which is the current page: $paged = ( get_query_var( ‘paged’ ) ) ? get_query_var( ‘paged’ … Read more
Not sure if you mean this kind of approach: add_filter( ‘paginate_links’, function( $link ) { return filter_input( INPUT_GET, ‘from_expired’ ) ? remove_query_arg( ‘from_expired’, $link ) : $link; } ); to remove the from_expired from the pagination links if it’s in the current GET query.
You can filter generated SQL and add precision parameters that you need. Enable filters for get_posts() by adding following to query: ‘suppress_filters’ => false, And: add_filter(‘posts_where’,’cast_decimal_precision’); function cast_decimal_precision( $where ) { return str_replace(‘DECIMAL’,’DECIMAL(10,3)’,$where); } Update With Jan’s suggestion: add_filter(‘get_meta_sql’,’cast_decimal_precision’); function cast_decimal_precision( $array ) { $array[‘where’] = str_replace(‘DECIMAL’,’DECIMAL(10,3)’,$array[‘where’]); return $array; }
Completely canceling main query is pretty much high level madness, that involves subclassing wp class. I would: Hook into pre_get_posts with is_main_query() check Run featured query (still inside hook) and stash results somewhere Use those results to set excluded posts on main query
twentyeleven_content_nav() uses the main query object, $wp_query. You’ll need to use the $wp_query variable, rather than $unfiltered_query, then wp_reset_query() to restore the original $wp_query (which it’ll find in $wp_the_query, something you should probably avoid touching directly). As long as you’re careful to restore the original query, you’re in good shape. I would submit a patch … Read more
You cannot use the same object of WP_Query twice. Therefore you need to create another one with a tax_query parameter to fetch posts which are not assigned to any term. //fetch all reviews which have no assigned term in ‘review-product’ $taxonomy = ‘review-product’; $post_type=”reviews”; $args = [ ‘post_type’ => $post_type, ‘tax_query’ => [ [ ‘taxonomy’ … Read more
You are using meta query without setting a value. The way you are doing it is using to query posts, not to order them. Using Named Meta Queries To order your posts by different meta datas, you can give your meta queries a name and then use that to set the ordering. Here is a … Read more