So I think there’s two solutions to this. Precalculate this value. I would suggest looking in to this if you can. Maybe hook into the post save hook and do a simple operation to save calculated price in a new meta value. This saves the below complicated code. It is possible to do this with … Read more
Meta queries are essentially wrapper for ease of setup, but end results is part of SQL query to run on MySQL database. These operators are those of MySQL, see in documentation: LIKE operator (performs pattern matching) IN() function (checks if value is in set)
The NOT IN and != comparison operators work fine, however be aware that if you are using meta then your data may not be working in the way you expect. Specifically, meta_keys don’t have to be unique per post. A post can have _no_interest set to 1 AND have another meta row with it set … Read more
WordPress 3.5 and up supports EXISTS and NOT EXISTS comparison operators. compare (string) – Operator to test. Possible values are ‘=’, ‘!=’, ‘>’, ‘>=’, ‘<‘, ‘<=’, ‘LIKE’, ‘NOT LIKE’, ‘IN’, ‘NOT IN’, ‘BETWEEN’, ‘NOT BETWEEN’, ‘EXISTS’ (only in WP >= 3.5), and ‘NOT EXISTS’ (also only in WP >= 3.5). Default value is ‘=’. http://codex.wordpress.org/Class_Reference/WP_Query … Read more
The other day I was thinking on how to make something like this, I would recommend to save the hottnes as a post meta value, that is updated on every vote, save or update, for that you will need the save_posts filter and then you can get the posts ordered with pre_get_posts and a meta … Read more
I figured out a solution myself. No javascript required, only another template function. URL building done manually. The idea is to use the hook ‘template_redirect’, check if the requested page is the corresponding store archive page, then check for $_REQUEST vars there and build a new URL. Finally redirect to this URL. function my_template_redirect() { … Read more
You need to set ignore_sticky_posts to true in your query arguments. This way you exclude sticky posts and only focus on the post ID’s array being passed to post_in ‘ignore_sticky_posts’ => true, EDIT If this does not make much sense, please see my answer here to similar question where I have explained it a bit … Read more
If you want both posts that have and do not have a meta key, you need an OR relation meta query to select both posts with key and those where it does not exist. $args = array( ‘meta_query’ => array( ‘relation’ => ‘OR’, array( ‘key’ => ‘_post_like_count’, ‘compare’ => ‘EXISTS’ ), array( ‘key’ => ‘_post_like_count’, … Read more
Filters are for modifying data that’s passed through them. You need to take the input, modify it, then return it. function exclude_not_allowed_terms( $args, $taxonomies ) { if(!current_user_can(‘edit_others_posts’) && in_array( ‘my-taxonomy’, $taxonomies ) ) { $args[‘meta_query’] = array( array( ‘key’ => ‘owner’, ‘value’ => get_current_user_id() ) ); } return $args; } add_filter( ‘get_terms_defaults’,’exclude_not_allowed_terms’, 20, 2 );
Q1 Yes, you can store serialized arrays as a single meta key, eg: update_post_meta( $post_id, ‘my_items’, array( 1, 2, 3, 4 ); Furthermore, you can store multiple values against a single meta key, eg: add_post_meta( $post_id, ‘my_items’, 1 ); add_post_meta( $post_id, ‘my_items’, 2 ); The latter is preferred because meta queries can be more efficiently … Read more