What you are about to read is the result of, probably, 20+ hours of banging my head against a wall. It wasn’t until Nick came in and showed me the light that I finally was able to get over the hump.
I was having a heck of a time getting a custom WordPress query that displays a random custom post from a custom taxonomy to work properly. I only seem to have this problem when returning information via a plugin or via a function in the theme, but it is possible that it might pop up elsewhere.
To clarify, I have a custom post type called “ads”. I have a custom taxonomy attached to the “ads” custom post type called “rotation”. Here is the code I finally went with:
global $post; $args = array( 'post_type'=>'ads', 'showposts'=>'1', 'orderby'=>'rand', 'tax_query'=> array( array( 'taxonomy' => 'rotation', 'field' => 'slug', 'terms' => $position, 'operator' => 'IN', ), ), ); $my_query = new WP_Query($args); while ($my_query->have_posts()) : $my_query->the_post(); // Display post details here. Example: the_title(), the_permalink(), etc. endwhile; }
The big hurdle to overcome was knowing that I needed to use the “tax_query” property. I still don’t know why that part is necessary, but it is. If you know why that is necessary, please share your knowledge in the comments.
I hope this information saves someone many hours of frustration! 🙂
More posts from themightymo.com
With ACF 5, they shipped a relatively-unknown and awesome feature: The ability to have WordPress automatically-save your ACF fields to a json file in your theme folder every time you save your fields. This has the effect of: All you need to do is add a folder called, “acf-json”, to your theme folder, and it…
How to use $current_user or is_user_logged_in() with FacetWP and WordPress to show different content for logged-in users
I have a membership site where I need to display certain FacetWP results to people who are logged in and other FacetWP results to people who are logged out. Unfortunately, FacetWP forgets WordPress’ global $current_user variable the minute you use one of the facets. Same with WordPress’ is_user_logged_in() function – FacetWP forgets it all once…
I was recently horrified to discover that the “wp_options” table of this site was over 1.3 gigabytes in size. For those of you counting at home – that is ENORMOUS and unnecessary. I was confused, because the table seemed to balloon overnight (and likely did balloon overnight, it turns out!). The issue was caused by…