Problem: I am using a View of taxonomy terms ordered by custom field value to show links to the next and previous term archives. I would like to filter those Views by term grandparent, so that only terms in the same grandparent are included in the results.
Solution: There is no term grandparent filter, so you can use another custom field in the Class Parts taxonomy. For each class, use a different field value. So for Knitting Superstar and all its descendant terms, use "knitting-superstar". For Fearless Knitter and all its descendant terms, use "fearless-knitter", etc. Then add a filter to the Next and Previous Views that filters by this custom field, set by a shortcode attribute. In the View shortcodes for the Next and Previous View, use a Types termmeta shortcode to insert the current term archive's custom field value in a shortcode attribute.
Problem: I am using term archives to display posts without pagination, and I would like to create Next and Previous links to paginate to another term archive page. The sort order should be determined by a custom field on the terms.
Solution:
Use Views filtered by term where the term ID is set by a shortcode attribute. Pass the current term's field value into the filter and sort by the term field value. Use the following custom shortcode to determine the current term's order.
Problem: I would like to create a hierarchical menu of taxonomy term links.
Solution: Use multiple nested Views of this taxonomy. Filter these Views by term ID or term parent, and output the term links and/or another nested View in each Loop.
Use the following custom shortcode to get the ID of an ancestor term at a specific level of hierarchy:
Problem: I would like to apply a different Layout to my custom taxonomy archives depending on the hierarchical level of the term.
Solution: Use custom code to programmatically select a specific Layout for each hierarchical level:
function apply_layout_by_archive_term_hierarchy( $id, $layout ){
// all the taxonomy slugs that should use these hierarchical layouts
$taxonomies = array( 'your-custom-taxonomy' );
// the layout IDs for each level of hierarchy, separated by a comma
$layouts = array( 123, 456, 456, 789 );
// ---------------------------------------------------
// you should not edit anything below
// ---------------------------------------------------
$layout_to_apply = $id;
$current_taxonomy = isset(get_queried_object()->taxonomy) ? get_queried_object()->taxonomy : null;
// test for the correct taxonomy archive
if( !$current_taxonomy || !in_array( $current_taxonomy, $taxonomies) )
return $layout_to_apply;
// find the hierarchical term level and apply the corresponding layout
$current_term_level = get_tax_level(get_queried_object()->term_id, $current_taxonomy);
if( isset( $layouts[$current_term_level])){
return $layouts[$current_term_level];
}
// fallback to original layout
return $layout_to_apply;
}
add_filter('get_layout_id_for_render', 'apply_layout_by_archive_term_hierarchy', 10, 2);
function get_tax_level($id, $tax){
$ancestors = get_ancestors($id, $tax);
return count($ancestors);
}
We document known issues and their solutions in Toolset errata. Save time by checking there first and seeing if what you are facing is a known issue. This list is kept short. We do our best to resolve all known issues with every release of Toolset plugins.
Support Policy
Toolset staff will help you use the Toolset plugins correctly, provide any information you need, help troubleshoot problems and advice on best-practices.
Please make sure to issue only one topic per each support ticket.
