Try this $args = array( ‘post_type’ => ‘events’, ‘meta_query’ => array( ‘relation’ => ‘AND’, array( ‘key’ => ‘fl_type’, ‘value’ => ‘Awards’ ), array( ‘key’ => ‘fl_expire’, ‘value’ => 0, ‘type’ => ‘NUMERIC’, ), array( ‘key’ => ‘fl_global’, ‘value’ => 1, ‘type’ => ‘NUMERIC’, ), ), ‘posts_per_page’ => -1, ‘meta_key’ => ‘fl_order’, ‘orderby’ => ‘meta_value_num’, ‘order’ … Read more
While the regexp solution will function, it quickly gets slower as the number of users increases. This is because the database cannot perform optimisation and indexing tricks, and forces a full table scan. The more users, and the more meta, the greater the cost of the query. At a minimum it requires caching to avoid … Read more
That’s not how meta_query works, the documentation at WordPress.org states that meta_query does not take parameters, but rather arrays of parameters meta_query also contains one or more arrays with the following keys: Then further down: Important Note: meta_query takes an array of meta query arguments arrays (it takes an array of arrays) – you can … Read more
This works although I have no idea why this and not that. Would like to see an explanation in an answer. Because that code sets the posts_per_page value to -1 which means no limit and it’s similar to setting nopaging to true, hence all found posts are returned. it reports finding all the posts with … Read more
You can find the post using get_posts() and the meta query (in my example, I used meta_key and meta_value) like so: See the function reference for more details on the parameters (and other examples that might help you), but the ‘fields’ => ‘ids’ means that the function will return only the post IDs and not … Read more
You are Storing multiple values into one single meta entry, instead of storing each value on its own meta entry (which would be the optimal approach). But still you can make it work that way. According to the docs, for the WP Query match operator you can use: Possible values are ‘=’, ‘!=’, ‘>’, ‘>=’, … Read more
Short answer is: Big Meta Queries are incredibly bad and can quickly lead to the MySQL-Server not responding anymore. You should try to rework the meta_query to not have so many clauses. Long Answer: Wordpress Post Metadata is stored incredibly inefficient when it comes to querying. Best advise would be to never ever EVER store … Read more
To do this you need to use named meta query clauses according to the official developer docs for WP_Query: ‘orderby’ with multiple ‘meta_key’s If you wish to order by two different pieces of postmeta (for example, City first and State second), you need to combine and link your meta query to your orderby array using … Read more
New answer I now have a better understanding of the question thanks to OPs comment and have come up with the following. Not tested! global $wpdb; /** * @var string $field The flexible content field name. */ $field = ‘a_flexible_content_field’; /** * @var string $layout The flexible layout name. */ $layout=”layoutTwo”; /** * @var string … Read more
The docs are a little vague in this area, but it should be possible to define your ordering value more succinctly: $args = array( ‘post_type’ => ‘post’, ‘post_status’ => ‘publish’, ‘posts_per_page’ => 5, ‘category__in’ => $postCategories, ‘meta_query’ => array( array( ‘key’ => ‘ordering_date’, ‘value’ => date(“Y-m-d H:i:s”), ‘compare’ => ‘>=’, ‘type’ => ‘DATETIME’, ), ), … Read more