Updated: The WP_User_Query class, in WordPress 4.1+, supports it with : ‘orderby’ => ‘include’ Since WordPress 4.7 there’s also support for: ‘orderby’ => ‘login__in’ and ‘orderby’ => ‘nicename__in’ So we no longer need to implement it through a filter, like we did here below. Previous Answer: I wonder if this works for you: add_action( ‘pre_user_query’, … Read more
Firstly, you are invoking an infinite loop, which causes the memory exhaustion. To avoid it, put the following at the beginning of your function: // avoid infinite loop remove_action( ‘pre_get_posts’, __FUNCTION__ ); It makes sure the you are not hooking it into pre_get_posts over and over again, re-initiating your get_posts() call over and over again. … Read more
<ul class=”products”> <?php $args = array( ‘post_type’ => ‘product’, ‘posts_per_page’ => 12 ); $loop = new WP_Query( $args ); if ( $loop->have_posts() ) { while ( $loop->have_posts() ) : $loop->the_post(); wc_get_template_part( ‘content’, ‘product’ ); endwhile; } else { echo __( ‘No products found’ ); } wp_reset_postdata(); ?> </ul><!–/.products–>
So, let’s say $query is your WP_Query object. I.e. $query = new WP_Query($some_query_args ); Then you can set up ‘the loop’, by $query->get_posts(); Then to check if there are actually any returned results: if ( $query->have_posts() ) : //Use a While loop to show the results else: //No results, let’s show a message instead. //This … Read more
Lets break it down step by step: if ($query->is_search && is_page_template(‘search’)) { There are 3 problems here is_page_template search.php isn’t a page template, that’s not how the search template is loaded. So this won’t work. But if it did work, there’s a new problem. Functions such as is_page_template etc rely on the main query, but … Read more
WordPress uses a lot of plugins and is very query heavy but the in spite of that, the front page uses 59 queries to generate itself. I think the default (on a vanilla WordPress install on the default theme) is 27 or something of that nature. The larger the number of queries, the slower the … Read more
It’s always advised to use $wpdb->prepare when you are taking input from user. This will help in protecting queries against SQL Injection. For more details, check the Codex When you use $wpdb->prepare, you must pass the variables to the query. In your case, you can skip using $wpdb->prepare as you are using a hard coded … Read more
There two things that you need to do to make this happen: 1) Create metadata for the data for each event 2) Query for the posts using meta_query For #1, you need to add a metabox that allows the user to add a date for the event. This data should be stored as metadata using … Read more
While this is really a MySQL question it does help to understand the WordPress SQL schema and also I love trying to optimize SQL queries so rather than send you off to StackOverflow I’ll try to answer you here. You may still want to post it over there to get some other opinions. And while … Read more
You can try this: /** * Add support for the “display_name” search column in WP_User_Query * * @see http://wordpress.stackexchange.com/a/166369/26350 */ add_filter( ‘user_search_columns’, function( $search_columns ) { $search_columns[] = ‘display_name’; return $search_columns; } ); where we use the user_search_columns filter to modify the available search columns. So what fields can we use with this filter? Here’s … Read more