Try changing hierarchical: false in your CPT definition (if your application allows). When CPT’s are set to hierarchical: true all posts will be queried in the admin dashboard which can cause memory issues.
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
I wouldn’t recommend using a taxonomy slug that coincides with the public query variables, like title. The title query variable was introduced in 4.4 so I think that could explain your problems. Check out this part of the WP_Query class: if ( ” !== $q[‘title’] ) { $where .= $wpdb->prepare( ” AND $wpdb->posts.post_title = %s”, … 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
not tested but give this a shot ‘tax_query’ => array( ‘relation’ => ‘AND’, array( ‘taxonomy’ => ‘image_tag’, ‘field’ => ‘term_id’, ‘terms’ => 25, ‘operator’ => ‘IN’, ), array( ‘taxonomy’ => ‘image_tag’, ‘field’ => ‘term_id’, ‘terms’ => 41, ‘operator’ => ‘IN’, ) ), OR ‘tax_query’ => array( ‘relation’ => ‘AND’, array( ‘taxonomy’ => ‘image_tag’, ‘field’ => … Read more
It’s not possible with WP_Query directly out of the box, but by using the posts_where filter to look for a custom argument on WP_Query, it is possible to add this functionality. Assuming starts_with is the name of the argument we want to use, we can filter posts_where to add a WHERE clause limiting results to … 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 been able to solve this myself. My entire code for registering the CPT: <?php add_action( ‘init’, ‘events_post_type_register’ ); function events_post_type_register() { $post_type = “events”; $labels = array( ‘name’ => _x(‘Events’, ‘post type general name’, ‘project_X’), ‘singular_name’ => _x(‘Event’, ‘post type singular name’, ‘project_X’), ‘add_new’ => _x(‘Add New’, ‘event’, ‘project_X’), ‘add_new_item’ => __(‘Add New Event’, … Read more
I’ve tried to sort this out before for my own purposes. As far as I can tell … post_type is not really set anywhere for the post post type. For the page post type I only see the post type key in queried_object. For CPT types there is a post_type key in query_vars and also … Read more
Assuming your custom post type is named “job_posting”, you just need to change your query to read: $query = new WP_Query( array( ‘post_type’ => ‘job_posting’ ) ); This can be found in the official documentation. There’s a lot more parameters you might like to use too – you can find a full list in the … Read more