Getting posts without a certain meta key is a little tricky, namely due to the database design and the nature of SQL joins. AFAIK, the most efficient way would be to actually grab the post IDs that do have the meta key, and then exclude them from your query. // get all post IDs that … Read more
This is a simple mathimatical problem. You will indeed need access to both your longitude and latitude, so save it in a metafield. than you will have to query your posts like this as a sql query. Haven’t got a chance to test it. and or pour it into wordpress. Don’t have access to my … Read more
There are different way to do the trick, 2 comes into my mind: use a complete custom $wpdb query use WP_Query with filters, using WP_Meta_Query to build the additional sql I’ll post here sample code for case #2 /** * Run on pre_get_posts and if on home page (look at url) * add posts_where, posts_join … Read more
If we define the conditions: A: my_custom_field_ignore EXISTS B: my_custom_field_ignore = 1 then NOT ( A && B ) is equivalent to: NOT ( A ) || NOT ( B ) meaning in our case: ( my_custom_field_ignore NOT EXISTS ) || ( my_custom_field_ignore != 1 ) We could therefore try the following for WP 3.5+ … Read more
You could try the REGEXP version: ‘meta_query’ => array( array( ‘key’ => ’email_address’, ‘value’ => ‘^hello@’, ‘compare’ => ‘REGEXP’, ) ) where ^ matches the beginning of a string. You can check the MYSQL reference on REGEXP here for more info. Notice that these are the possible values of the meta compare parameter: ‘=’, ‘!=’, … Read more
I’ve come across this problem and it seems MySQL doesn’t deal well with the multiple joins to the same table (wp_postmeta) and OR-ed WHERE that WP generates here. I dealt with it by rewriting the join and where as mentioned in the post you link to – here’s a version that should work in your … Read more
Adding a custom endpoint is pretty straightforward. I also modified the url to look more like http://example.com/wp-json/namespace/v2/posts?filter[meta_value][month]=12&filter[meta_value][year]=2015 function wp_json_namespace_v2__init() { // create json-api endpoint add_action(‘rest_api_init’, function () { // http://example.com/wp-json/namespace/v2/posts?filter[meta_value][month]=12&filter[meta_value][year]=2015 register_rest_route(‘namespace/v2’, ‘/posts’, array ( ‘methods’ => ‘GET’, ‘callback’ => ‘wp_json_namespace_v2__posts’, ‘permission_callback’ => function (WP_REST_Request $request) { return true; } )); }); // handle the request … Read more
This seems to be a bug in WordPress. WordPress actually modifies the meta_query if you specify orderby and meta_key as query vars. Normally this modification adds the new meta_key as the first array in meta_query array and hence the orderby is applied to the first meta key specified in meta_query. But when you modify orderby, … Read more
Note that the relation part in the meta_query argument, is only used to define the relation between the sub meta queries. You can try this setup: $args = [ ‘_meta_or_title’ => $thesearch, // Our new custom argument! ‘meta_query’ => [ [ ‘key’ => ‘model_name’, ‘value’ => $thesearch, ‘compare’ => ‘like’ ] ], ]; where we … Read more
Here’s one experimental idea: Assume we got: post A with the custom field location1 as UK – London post B with the custom field location2 as France – Paris post C with the custom field location3 as USA – New York Then we could use, for example: $args = [ ‘meta_query’ => [ ‘relation’ => … Read more