The problem is with the arg ‘meta_key’ => ‘meta_value’ – meta_key isn’t needed if you have a meta_query arg (despite what the codex appears to say) and its value here doesn’t make sense anyway – so just remove it. However it does point out a behavioural change in 4.1 as before the meta_key was ORed … Read more
Ok, I managed to get it working by hooking into the ‘request’ filter, then checking to see if the last segment is term or not. If it’s not, change the $request var: function alter_the_query( $request ) { $dummy_query = new WP_Query(); // the query isn’t run if we don’t pass any query vars $dummy_query->parse_query( $request … Read more
Yeah I can imagine that query is going to be a doozy. The main reason for that is that every extra condition against a post meta value might be causing an extra SQL JOIN between the wp_posts table and the wp_posts table, and JOINS can get exponentially expensive. I’m surprised it even comes back in … Read more
Try using paginate_links( $args ). Here is code adopted from codex. $paged = ( get_query_var( ‘paged’ ) ) ? absint( get_query_var( ‘paged’ ) ) : 1; $args = array( ‘posts_per_page’ => 30, ‘paged’ => $paged, ); $the_query = new WP_Query( $args ); // the loop etc goes here.. $big = 999999999; echo paginate_links( array( ‘base’ … Read more
Old answer (which no longer works): A sneaky way to do it using MySQL, assuming the number’s always at the end, is to reverse the title, convert it to a number (+0), and then reverse again and convert it to a number: function wpse174646_posts_orderby( $orderby, $query ) { if ( $query->get( ‘orderby’ ) != ‘title_number’ … Read more
There is no straightforward way to do this– at least not one that I see. That is, there don’t seem to be any hooks specifically intended for this task. You still have options though. This is what I’d do: First, deny changes. function deny_post_date_change( $data, $postarr ) { unset( $data[‘post_date’] ); unset( $data[‘post_date_gmt’] ); return … Read more
@Uffo I would say your args are wrong, should be something like: $args = array( ‘post_type’ => ‘Event’, ‘posts_per_page’ => 1000, ‘meta_query’=> array( array( ‘key’=>’event_informations_show_on_the_homepage’, ‘value’=> ‘Show on the homepage’, ‘compare’ => ‘==’ ) ), ‘meta_key’=>’event_informations_date’, ‘orderby’=>’meta_value_num’, ‘order’=>’ASC’ ); The way you did it, it’s just the last meta_key that will be used both for … Read more
It’s not the plugin that is causing the issue it is the fact you are not querying the database correctly. It is not looking for integers your value is currently being stored as a string. To fix this you need to somehow change the value to a integer before it is passed to your array.
You set offset param, so paged param is ignored 😉 From Codex: offset (int) – number of post to displace or pass over. Warning: Setting the offset parameter overrides/ignores the paged If you want to ignore most recent post in this query, you can achieve it in two ways. 1. Custom pagination. $ppp = get_option(‘posts_per_page’); … Read more
The Codex link already has anything you seem to be after. Maybe you just didn’t know how to use the parameters… I would do this by means of a date_query: $args = array( ‘post_type’ => ‘post’, ‘post_status’ => array( ‘publish’, ‘future’, ), ‘date_query’ => array( array( ‘after’ => strtotime( ‘now’ ), ‘before’ => strtotime( ‘+1 … Read more