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
There is no need to do an overrated amount of queries to accomplish this. you can still use only one query, the_posts filter and some PHP to sort your code as needed. I take that this is a custom query from what I read in your question, so we can do the following: First, we … 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
If you hook your localize script function to wp_enqueue_scripts, then you will have access to the global $post variable. As long as you pick a hook at or after ‘wp’ you should have access to the global $post. <?php add_action(‘wp_enqueue_scripts’, ‘YOUR_NAME_scripts’); function YOUR_NAME_scripts() { wp_enqueue_script(‘YOUR_NAME-js’); global $post; $params = array( ‘site_url’ => site_url(), ‘admin_ajax_url’ => … Read more
If your extra data directly references a post meta you don’t have to do anything, because WP_Post implements the »magic« methods __isset() and __get() which directly asks for post meta keys (except for the following four keys: page_template, post_category, tags_input and ancestors). Here’s a quick example that shows the behavior: <?php $post_id = 42; $meta_key … Read more
I am not sure from your wording if you hadn’t tried it with query argument or it didn’t work? $the_query = new WP_Query(array( ‘meta_key’ => ‘open’, ‘meta_value’ => ‘yes’ )); Custom Field Parameters in Codex.
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