This thread is resolved. Here is a description of the problem and solution.
Problem: I have two custom taxonomies, TaxA and TaxB. I would like to create a filtered list of posts organized by taxonomy term in a nested format where TaxA is the top-level structure, with all TaxB terms nested inside each TaxA term, and filtered posts displayed beneath TaxB terms.
Solution: Use a series of nested Views filtered by shortcode attributes.
Relevant Documentation:
https://toolset.com/documentation/user-guides/passing-arguments-to-views/
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | - | - |
| 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | - | - |
Supporter timezone: America/New_York (GMT-04:00)
This topic contains 4 replies, has 2 voices.
Last updated by 5 years ago.
Assisted by: Christian Cox.
Hi, the trick here is how to pass the taxonomy terms into the View's query filter. I would start out by creating a View of taxonomy A, and include the term title in the loop. Then I would create a View of taxonomy B, and include the term title in the loop. Now insert View 2 in the loop of View 1. Place View 1 somewhere on the site. You should see the nested terms appear, but no posts.
Next, create a View of CPT posts (will call it View 3 here) and open up the Query Filter panel. Add two taxonomy term filters, one for taxonomy A and another for taxonomy B. Configure the filters so that the term slug is set by one shortcode attribute, and choose different attributes for taxonomy A and taxonomy B. Take a look at the screenshot here for more details about that.
Now you need to pass the term slugs from taxonomy A and taxonomy B into the View of CPT posts. Place the View 3 shortcode in the loop of View 2, and add the Tax B slug in the Tax B attribute you specified in the Query filter. In my example, the View 3 shortcode would now look like this:
[wpv-view name="my-view-3-slug" wpvbooktax="[wpv-taxonomy-slug]"]
Next you need a way to pass the taxonomy slug from Tax A into the View of Tax B, so you can place that slug in the View shortcode as well. So you'll have to go back to View 1 and find the shortcode where you inserted View 2. Now add the Tax A slug to that shortcode using any arbitrary shortcode attribute:
[wpv-view name="my-view-2-slug" mytaxa="[wpv-taxonomy-slug]"]
So now you have access to the mytaxa shortcode attribute in View 2, and you can add that value to the View 3 shortcode attribute using the wpv-attribute shortcode like so:
[wpv-view name="my-view-3-slug" wpvbooktax="[wpv-taxonomy-slug]" wpvflattax="[wpv-attribute name='mytaxa']"]
This technique is called passing arguments to Views, and is explained in greater detail here: https://toolset.com/documentation/user-guides/passing-arguments-to-views/
