I’ve been combing this site and google for the answer and I’ve come up completely empty. Basically I want to do exactly what this post asks, but I need a hierarchical taxonomy. The answer given in that post works great, but only with a single level taxonomy. Is it possible to do what I want? I’ve tried a million things, but none work, at best I can get the right permalinks but they come up 404.
To visually illustrate what I want:
/basename/ - ideally a page, but I think this will cause a permalink collision
/basename/top-cat/ - top parent custom taxonomy archive
/basename/top-cat/child-cat/ - child cat custom taxonomy archive
/basename/top-cat/child-cat/grandchild-cat/ - grandchild cat custom taxonomy archive
/basename/top-cat/child-cat/grandchild-cat/post-name/ - my custom post type post
You can do this fine with the built in posts and categories, how do you do it with custom taxonomies and custom post types? I know that you need to use 'rewrite' => array( 'slug' => 'tax-name', 'with_front' => true, 'hierarchical' => true ),
to get hierarchical slugs, which works fine on the archive pages, but the custom post type posts come up 404. If I remove the 'hierarchical' => true
part then the posts work, but I lose the hierarchical urls (only /basename/grandchild-cat/post-name/ works).
So, any solutions? Thank you so much, this has been driving me nuts for about 3 weeks now.
After combining a bunch of pieces of other answers I got it working! So here’s the solution for those of you who are struggling with this too:
This post and this one helped me out some, so thanks to those guys.
Note, all this code, plus your initial custom post type and taxonomy registration code goes in your
functions.php
file.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 justbasename
. Don’t forget to also add'hierarchical' => true
to the taxonomy rewrite array to get nested terms in your url. Also make surequery_var
is set totrue
in both cases.You need to add a new rewrite rule so WordPress knows how to interpret your url structure. In my case the custom post type part of the uri will always be the 5th uri segment, so I defined my match rule accordingly. Note that you may have to change this if you use more or less uri segments. If you’ll have varying levels of nested terms then you’ll need to write a function to check whether the the last uri segment is a custom post type or a taxonomy term to know which rule to add (ask me if you need help on that).
Then you need to add this code to let workpress how to handle
%taxonomy_name%
in your custom post type rewrite slug structure:I created a custom function based on WordPress’s own
get_category_parents
:Then you need to flush your permalinks (just load your permalinks settings page).
Now everything ‘should’ work hopefully! Go make a bunch of taxonomy terms and nest them correctly, then make some custom post type posts and categorize them correctly. You can also make a page with the slug
basename
, and everything should work the way I specified in my question. You may want to create some custom taxonomy archive pages to control how they look and add some kind of taxonomy widget plugin to show your nested categories in the sidebar.Hope that helps you!
Take a look at
this plugin(now on github). It provides hierarchical URLs for categories, but you can easily adapt to any taxonomy.The rule creation follows a recursive function.
For dealing with varying level of nesting,
I ended up using Jeff’s solution without the
rewrite_rules_array
filter. Instead I used therequest
filter to check if the last url part is a valid postname and add it to the query_vars.eg.
Here is my take on Jeff’s solution. The
rewrite_rules_array
may not be needed depending on what your application is. This simplifies thefilter_post_type_link
and does not require any additional functions. It uses the built-in get_term_parents_list()