The problem is that you’ve interpreted wpdb::esc_like as a literal copy paste, and not a direction, and used it as a static function, when it is not a static function. Good: global $wpdb; $foo = $wpdb->esc_like( $bar ); Bad: $foo = wpdb::esc_like( $bar ); Other things to note: The & in &$wp_query ) is a … Read more
I believe the problem is that you are using single quotes in passing values to query (e.g. ‘value’ => ‘$bedrooms’), but this way the variables are not expanded (see http://php.net/manual/en/language.types.string.php). Simply use ‘value’ => $bedrooms.
You might try $query->set( ‘ignore_sticky_posts’, 1 ); to stop the sticky posts from being prepended.
In both examples, you are searching between ‘max’ and ‘min’, where it should be between ‘min’ and ‘max’: array( $dist[‘max_latitude’], $dist[‘min_latitude’] ) ‘value’ => $dist[‘max_latitude’], ‘compare’ => ‘>=’); ‘value’ => $dist[‘min_latitude’], ‘compare’ => ‘<=’); Both mean: “Search for a value that ist greater than max_latitude and less than min_latitude” Another finding why my own meta_query … Read more
UPDATE: Sorry, apparently my solution faces the same problem when the query contains values such as ‘$599,000’ or ‘$1,149,000. so far, the only solution so far was cleaning the database imported data values to INT/UNSIGNED (even though, meta_value is saved as TEXT). However, the meta ordering by value still don’t work quite as it should. … Read more
You are not querying/saving the correct meta_key. For example, looking at your code, you pass $typename variable to update_post_meta() as meta_key and $typename=”events”. But later in the query you are querying for meta_key = date. Also, you pass $meta as meta_value and in your actual code $meta is an array containing multiple values (location, date, … Read more
You are not going to this in one query, you will need to do two queries. The first query will hold the posts which will hold the meta key, the second will be the posts without the meta key. (Just a note: never use query_posts unless you intentionally wants to break things) You can try … Read more
The answer is, this can”t be done with any efficiency. The best thing to do is pull the data out of the serialized array and save each as their own key/value pair in the wp_usermeta table. My key was extraInfo and the values I needed were serialized in the value. This is the script I’ve … Read more
Per the comment from @ialocin I switched from WP JSON API to WP REST API. There is much less documentation with the rest api but it’s customizable using native wordpress functions. Also, it has a nifty github plugin for allowing use with ACF custom fiends. Anyway, the documentatino for customization the wp rest api is … Read more
The way you are trying to do it is probably the wrong way. WP_Query does not have any build in feature to subtract the values from two custom fields and then returning (or ordering) posts according to the value of the subtraction from the two fields. You can probably filter the generated SQL via the … Read more