If you have a lot of products, probably a custom sql query is a better option. I’d probably recommend following that route either way. Custom queries may be ‘icky’, but it’ll lighten resources and be a darn slight quicker in most cases* I’ve written a function that does most of the labour, and may well … Read more
I think you should add support for custom taxonomy types and name the file taxonomy-cpt-type.php where cpt is the name of your Custom Post Type. Your CPT archive file should be named archive-cpt.php where cpt is the name of your Custom Post Type. Here’s all the code which has been tested. Note: You shouldn’t be … Read more
Categories and Taxonomies are not exactly the same. A category is a default taxonomy You can use categories with custom post types however its better to use custom taxonomies because the truth is, they are an extremely powerful way to group various items in all sorts of ways. add_action( ‘init’, ‘wpsites_custom_taxonomy_types’ ); function wpsites_custom_taxonomy_types() { … Read more
try this: <?php get_header(); ?> <? // get the current term $term = get_term_by( ‘slug’, get_query_var( ‘term’ ), get_query_var( ‘taxonomy’ ) ); <div class=”container” role=”main”> <h1 class=”entry-title”><?php echo $term->name; ?></h1> <div class=”entry-content ref”> <?php $loop = new WP_Query( array( ‘post_type’ => ‘references’ , ‘genre’ => $term->slug) ); ?> <?php while ( $loop->have_posts() ) : $loop->the_post(); … Read more
That is expected and how Template Hierarchy works. I know there was a track ticket raised a couple of years ago regarding this issue if to an index for archives should be introduced in core or not. (EDIT: Found the ticket, check it out here: Ticket #13816 There should be built-in index pages for taxonomies) … Read more
Edited because I had completely misread question. To know if term is a parent or not, we need access to term post parent, so is better to replace more specialized methods istead of walk(). That said, I understand that code in OP uses class definition inside the function to avoid fatal error because of Walker_Category_Checklist … Read more
try using this fancy function that group the posts by term id that Scribu and Mike created: function event_clauses( $clauses, $wp_query ) { global $wpdb; if ( isset( $wp_query->query[‘orderby’] ) && ‘event_location’ == $wp_query->query[‘orderby’] ) { $clauses[‘join’] .=<<<SQL LEFT OUTER JOIN {$wpdb->term_relationships} ON {$wpdb->posts}.ID={$wpdb->term_relationships}.object_id LEFT OUTER JOIN {$wpdb->term_taxonomy} USING (term_taxonomy_id) LEFT OUTER JOIN {$wpdb->terms} USING … Read more
This turned out to be a quite extensive little project for me. BASIC IDEA My approach was to go with a custom archive page as this seems to be the best approach here. The thing with custom taxonomies is that if you have a structure in place, changing that would become a real messy expedition. … Read more
You have: A rewrite rule that handles the post being in the 5th part A rewrite rule to handle the taxonomy part A rewrite rule to handle the post being in the 2nd or 3rd part isn’t in the above list, hence why you get a 404. If we take this rewrite rule: $newRules[‘basename/(.+)/(.+)/(.+)/(.+)/?$’] = … Read more
Replace your code with the following. I have made some changes to the post_type_link filter’s callback function. function my_custom_post_work() { $labels = array( ‘name’ => _x( ‘Work’, ‘post type general name’ ), ‘singular_name’ => _x( ‘Work’, ‘post type singular name’ ), ‘add_new’ => _x( ‘Add New’, ‘book’ ), ‘add_new_item’ => __( ‘Add New Work’ ), … Read more