Given that this order you desire is unfortunately not alphabetical (although that wouldn’t be very scaleable… but it would be handy). You might make life easier on yourself by adding another custom field called (say) “display_order”. Then add the numbers 1,2 and 3 to that field, and then query the post type ordering by these … Read more
Try to wrap true with quotes <?php $event =array( ‘post_type’ => ‘Events’, ‘posts_per_page’ => 1, ‘meta_query’ => array( array( ‘key’ => ‘front_event’, ‘value’ => ‘true’ )) );?>
Assuming the rest works, why not order the normal way: function sort_posts_orderby( $orderby ) { $orderby = ‘wp_postmeta.meta_value ASC, wp_posts.post_date DESC’; return $orderby; }
You need to sort in descending order so the last 5 posts will be on top. Just add ‘order’ => ‘DESC’ to your args. $args = Array( ‘post_type’ => ‘post’, ‘posts_per_page’ => ‘5’, ‘meta_key’ => ‘views’, ‘orderby’ => ‘meta_value_num’, ‘order’ => ‘DESC’ );
Note: Only read briefly, so I might missunderstood your Q. JOIN on meta_query/post_meta table is pretty … hm, funny(?) … as you’ll JOIN the table (again) for every key you add – this is a known problem (read on trac). In detail INNER JOIN wp_postmeta ON (wp_posts.ID = wp_postmeta.post_id) is the same as INNER JOIN … Read more
As Kaiser has pointed out, the meta_value => $todaysString is querying for events where the value for key event_date is equal to todays string. I.e. events happening today. Also, from the fact that you’ve used strtotime suggests you are sorting by timestamp – which you would like interpreted (and sorted as) a number rather than … Read more
You have a typo in orderby, and meta_value_num is only used as an orderby value, try this: $args = array( ‘post_type’ => ‘event’, ‘tax_query’ => array( array( ‘taxonomy’ => ‘locations’, ‘field’ => ‘id’, ‘terms’ => $location // location term id ) ), ‘meta_key’ => ‘event_date’, // this meta field stores event date in yymmdd format … Read more
add_filter(‘pre_get_posts’, ‘customize_query’); function customize_query($query) { if($query->is_main_query() && ($query->is_search() || $query->is_archive()) { $query->set(‘update_post_meta_cache’, false); $query->set(‘update_post_term_cache’, false); } } Then wordpress will make 2 less queries for those pages & then you can use the $wpdb object to write custom queries.
First of all, one never should rely on raw $_REQUEST: believe me, this is a security issue. PHP has 2 functions: filter_input and filter_input_array that helps you to sanitize your request data. In addition, in your request dump I don’t see any $_REQUEST[‘custom_bath’], but you are using that value, that can be a cause for … Read more
get_posts() is a rather generic wrapper for retrieving set of posts and just that. As such it purposely unmakes some of the arguments typical for loops. Specifically it ignore stickies: $r[‘ignore_sticky_posts’] = true; So if you want more loop-like behavior you should be using instance of WP_Query object instead.