Thanks to @Howdy_McGee. He gave me the hint to look after serialized meta queries. With this code I get the desired result. $args = array( ‘posts_per_page’ => -1, ‘orderby’ => ‘post_date’, ‘order’ => ‘DESC’, ‘post_status’ => ‘publish’, ‘meta_query’ => array( array( ‘key’ => ‘enterprise_on_page’, ‘value’ => serialize(strval(‘trainees’)), ‘compare’ => ‘LIKE’, ), ), ); $enterprise_posts = … Read more
Taxonomy queries are by default extremely complex relative custom field queries. Without benchmarking I am pretty sure they are going to be slower even if the meta table isn’t indexed, but you can add an index if you want. It won’t effect WordPress at all. My advice is “use what logically works for the data”. … Read more
The easiest way to have page nav for the custom post is to use WP PageNavi. After activating this plugin you need to add the following code in your custom post template. <?php if(function_exists(‘wp_pagenavi’)) { wp_pagenavi( array( ‘query’ =>$loop )); }
Add this code in functions.php. Use orderby with meta_value_num and define meta_key in argument array. add_action( ‘pre_user_query’, ‘wps_pre_user_query’ ); function wps_pre_user_query( &$query ) { global $wpdb; if ( isset( $query->query_vars[‘orderby’] ) && ‘meta_value_num’ == $query->query_vars[‘orderby’] ) $query->query_orderby = str_replace( ‘user_login’, “$wpdb->usermeta.meta_value+0”, $query->query_orderby ); }
It is terms (plural) not term (singular) in tax query arguments. 🙂
It appears that your first and second query are identical. Perhaps you should add an ‘offset’ param in your second query. $args = array( ‘posts_per_page’ => 3, ‘orderby’ => ‘most_recent’, ‘offset’ => 3, );
Do not run custom queries in place of the main query on the home page and any type of archive page. This will always cause an issue. If you need to alter the main query, use pre_get_posts to do so. To solve this issue, you need remove your code from your category page and go … Read more
Regardless of whether you registered new_var as a query_var, all GPC data (GET, POST, COOKIE) should be considered tainted. Basically, this data is user input. This means that you will need to clean and validate the data anyway. Common cleaning methods include casting the variable to a certain type (like integer or string), using a … Read more
@JasCav Here is something to put you in the right direction. Maybe someone can edit where needed. // args $args = [ ‘post_parent’ => $post->ID, ‘post_type’ => ‘page’, ‘posts_per_page’ => 8, ‘paged’ => get_query_var( ‘paged’ ), ‘meta_key’ => ‘team_school’, ‘meta_value’ => $school_type, ‘orderby’ => ‘wpse_last_word’, //<– make filter for ordering! ‘order’ => ‘ASC’ ]; // … Read more
How I have done custom queries in the past is use $wpdb->get_col() and just returned an array of IDs of the posts. Then I pass that to a get_posts() passing the IDs to the post__in parameter. That way you can then use WP standard controls.