The WP_Query documentation on the codex specifically says: ‘attachment’ – an attachment. Whilst the default WP_Query post_status is ‘publish’, attachments have a default post_status of ‘inherit’. This means no attachments will be returned unless you also explicitly set post_status to ‘inherit’ or ‘any’. I am not sure why it was working before because this is … Read more
Couple of things – avoid query_posts, use a new query object or the get_posts function (read all about it). And the_ID() echo’s the ID, use get_the_ID() instead. However, you can save some memory and processing by simply iterating over an array of posts (i.e. not using a proper “loop” and setting up the global post), … Read more
I got it ! Here is my final code for people who will search for similar problem 🙂 in functions.php : function se190254_custom_sql_for_search( ) { global $wpdb; //For security escape the search parameter $search_string = esc_sql($_GET[‘s’]); //Build the SQL request with $wpdb->base_prefix for “portability” $sql = “SELECT SQL_CALC_FOUND_ROWS {$wpdb->base_prefix}posts.ID FROM {$wpdb->base_prefix}posts LEFT JOIN {$wpdb->base_prefix}icl_translations t … Read more
You shouldn’t use query_posts functions. You should create instance of WP_Query class In your theme folder create a new file called category-slug.php. You can copy the category.php file or archive.php file to create category-slug.php file. Then in the new category-slug.php file before the while loop you can write your query. $query = new WP_Query( ‘category_name=apple,pears’ … Read more
Your basic query logic looks fine assuming you want an AND relationship between the first, middle, and last names but query_posts is never, ever, ever the right way to do anything. Note: This function isn’t meant to be used by plugins or themes. As explained later, there are better, more performant options to alter the … Read more
You’re right. It isn’t a good structure. You are running three queries on the page– the two you are creating plus the main query that is being completely ignored (plus ancillary queries). You are also clobbering the main query halfway through the page load when you overwrite $wp_query, which can cause unexpected and unpredictable results … Read more
I’d do it like this: $excluded_posts = array(); // select first 3 featured posts ordered by date $args = array ( ‘post_type’ => array( ‘post’ ), ‘category_name’ => ‘featured’, ‘posts_per_page’ => ‘3’, ‘order’ => ‘DESC’, ‘orderby’ => ‘date’, ‘ignore_sticky_posts’ => true, // or maybe not? ); $query = new WP_Query( $args ); while ( $query->have_posts() … Read more
Per comments, just use pre_get_posts filter (no query_posts()) very much as you have it with a few adjustments, eg test for $query->is_category( ‘news’ ) so that it only runs on news queries, and set the default to “2014” rather than bailing on no $_GET, eg function wpse129223_custom_meta_query( $query ) { // If not on the … Read more
Assusming you are using V1 of the WP-API, did you tried the following endpoint: http://www.example.com/wp-json/posts?filter[category_name]=pink+warm I’m looking at the code in WP_JSON_Posts class and the get_post() should be able to handle that use case. UPDATE: It seems there is a limitation with the way the query is built. Here is a potential workaround: add_filter(‘json_query_var-category_name’, function( … Read more
You need to swap their arguments & rel tag too: <?php echo str_replace( ‘rel=”next”‘, ‘rel=”prev”‘, get_next_post_link( ‘%link’, _x( ‘<span class=”meta-nav”>←</span> %title’, ‘Previous post link’, ‘twentythirteen’ ) ) ); ?> <?php echo str_replace( ‘rel=”prev”‘, ‘rel=”next”‘, get_previous_post_link( ‘%link’, _x( ‘%title <span class=”meta-nav”>→</span>’, ‘Next post link’, ‘twentythirteen’ ) ) ); ?>