Intercept the query on the posts_where filter. In there you can do a replacement of the non numeric values: preg_replace( “/[^0-9,.]/”, “”, $yourMeta ); Or in a (generic) code piece: add_action( ‘posts_where’, ‘wpse120784WhereDiameter’, 100 ); function wpse120784WhereDiameter( $where ) { // If conditions here – only target the cases where we need it # if … Read more
Try adding this to the top of your script: require(‘/path/to/httpdocs/wp-blog-header.php’); global $wpdb; Then you can run queries using: $sql = “Your SQL Query Here”; $wpdb->get_results($sql)
For each post add each term to a PHP associative array: foreach ( $posts as $post ) { $term_objects = get_the_terms( $post->ID, $taxonomy_name ); foreach ( $term_objects as $term_object ) { // Store term objects by term name. $terms_list[ $term_object->name ] = $term_object; } } Let’s say Bob was listed as the cook on the … Read more
Here is the general logic that can be used to fetch the child custom posts What I’ve assumed here is, You create a county post, then you create a area post and from parent metabox you select the desired county post and save the post id in post_parent function wpse_128630_cp( $post_type=”county”, $post_parent=””, $posts_per_page = -1 … Read more
Ha… While this makes a lot of sense, WP is not to good with arbitrary conditions like this and nothing like is implemented in WP_Query currently. However since your issue is really chronological rather than requiring dealing with IDs, you probably can make use of Date Parameters to restrict results to be older than time … Read more
Have a look on the date_query parameter that has been added to WP 3.7 WP_Query#Date_Parameters and the author parameter. Combine the two parameters as you need them to query all posts an author created in a given time: <?php $args = array( ‘posts_per_page’ = -1, // get all posts ‘author’ => get_the_author_meta( ‘ID’ ), // … Read more
Just unsetting the cat variable probably isn’t enough. The pre_get_posts hook happens after the query variables have already been parsed. So there’s probably a tax_query with the taxonomy = category and the terms = your category. You’re already dumping the $query in your code, presumably for debugging. So, look at what you’re actually dumping. Do … Read more
I believe there are different ways of achieving this. Simplest way I could imagine is as below: $featured_content_query = new WP_Query( array( ‘post_type’ => ‘feature’, ‘offset’ => 1, ‘posts_per_page’ => 10, ‘order’ => ‘ASC’ ) ); shuffle( $featured_content_query ); //PHP function to randomise posts array You can then continue to use $featured_content_query as usual!
I have worked out on your problem and have come up with a solution(as far I have understood the problem). It’ works like this: Registering a post type called : sliders with a taxonomy called slider. This will create a post type where you can store all your sliders and categories them with this custom … Read more
There is no reason that query should behave differently on a single post page than on any other page. That is, there is no reason in the code posted. The only thing that I can think of would be that there is a filter interfering– perhaps a poorly written filter on pre_get_posts or post_limits. You … Read more