There is a quick and somewhat dirty potential solution to this. I say ‘potential’ because I can’t spot the problem by looking at the code. I only have my suspicions. Instead of passing a separator like that. Try trailingslashit. } else $chain .= trailingslashit($name); return $chain; I am guessing at where the problem is based … Read more
As @Milo’s pointer said, this: Sadly, is normal WordPress behaviour. Can be suppressed using parse_tax_query and include_children set at 0… The code found in the answer at https://wordpress.stackexchange.com/a/202773/39300 Works for me… function taxonomy_archive_exclude_children($query){ $taxonomy_slugs = [‘product_category’, ‘application_category’]; if($query->is_main_query() && is_tax($taxonomy_slugs)){ foreach($query->tax_query->queries as &$tax_query_item){ if(empty($taxonomy_slugs) || in_array($tax_query_item[‘taxonomy’], $taxonomy_slugs)){ $tax_query_item[‘include_children’] = 0; } } } } add_action(‘parse_tax_query’, … Read more
Thanks for referencing my solution. You forgot one part though – defining the rewrite of your cpt. From my solution: First get your slugs right when defining your custom post types and taxonomies: for the custom post type it should be basename/%taxonomy_name% and the slug for your taxonomy should be just basename. Dont forget to … Read more
There is of course the include_children parameter for WP_Query as part of the taxonomy parameters. Which I suppose should work like this for you: $args = array( ‘tax_query’ => array( array( ‘include_children’ => false ), ), ); $query = new WP_Query( $args ); Or via parse_tax_query for your category archive: add_filter( ‘parse_tax_query’, ‘wpse163572_do_not_include_children_in_category_archive_parse_tax_query’ ); function … Read more
To see how we can make this work, have a read through the Query Overview Codex page, particularly the What Plugins can Modify section: Modify the query specification, after variable values are saved (request filter or parse_request action; if you want to use conditional tag tests, use the parse_query or pre_get_posts action, as these run … Read more
Use the deepest term only. If you want to rearrange the term relations later you don’t have to go through all posts to fix the post-term relations. Plus, you are more flexible when you want to separate the posts with child terms from post associated with the current term only.
One custom post type cannot be the child of another. hierarchical means: Each post can have children of the same post type, like pages. If you need relationships between different post types use the Posts 2 Posts plugin. Another option would be a custom hierarchical taxonomy for two post types. You could use it to … Read more
You can use pre_get_posts filter to filter out what you need. There’s an example on how to do this in Codex: https://codex.wordpress.org/Plugin_API/Action_Reference/pre_get_posts#Exclude_Pages_from_Search_Results function search_filter($query) { if ( !is_admin() && $query->is_main_query() ) { if ($query->is_search) { $query->set(‘post_type’, ‘post’); } } } add_action(‘pre_get_posts’,’search_filter’); Also, this article might get you in the direction of editing the search form…
Short answer: No, it does not have any impact at all. Longer answer: The ‘Order’ field is a remnant from the early days of WordPress. Its only purpose is to order the pages in the admin for easier content management. Plus, people can use it to display a list of pages in their preferred order, … Read more
Is there a better way to do this using custom taxonomies? You’re right on the money there. Rather than try to make a custom post into the child of a standard post (because you can’t), I’d recommend using a custom taxonomy to order things. Essentially, you could build a custom hierarchical taxonomy and use it … Read more