Terms filter issue

[boera]

Hi, I’ve created a blog page (https://framexec.com/welcome/resources/) using the ‘terms’ element to create filtering options. However, they do not behave as expected when using the menu. Two issues:

1. ‘Categories’ filter

On the main blog page I get the specified categories as expected:

However, if I go to one of the categories, only that category will then show on repeat in the drop down menu:

What do I need to do to ensure the full menu comes up, and the links work on every page?

These are the settings used for the categories:

2. ‘Our Specialist Practices’ filter

Meanwhile, the ‘Our Specialist Practices’ drop down shows the full menu regardless of the page, but the links only work from the main blog page, and are unresponsive from the tag or category archive pages (they work from author pages). These are permalinks, same as the All button, but whilst the All button work on all pages, the items in the drop down menu don’t. Again, what am I doing wrong here?

3. Taxonomies

Lastly, links in the ‘Our Specialist Practices’ are for tags. I tried using a looper for these, but I can only get categories to show in loopers, not tags, hence using permalinks instead. I would prefer using the query builder to specify tags - is this possible? If so, what am I doing wrong?

Thank you in advance!

[tristup]

Hi @boera,

Thanks for reaching out.
What you are expecting requires customization which is beyond the scope of Theme Support, I would suggest you hire a developer who can assist you to do the customization or you can avail of our newly launched service called TOTAL CARE, where we offer small customizations.

Thanks

[boera]

Thank you for responding. However, I don’t think this requires customization, rather it’s an issue with the query builder in the first drop down. Basically this: how do I specify which categories to include in the terms, as opposed to showing all terms?

Having tried and tested a few things, I’ve managed to get the second drop down to work. This is now a looper set to ‘all terms’ with tags, and all is well.

For the first drop down, this also works fine when set to ‘all terms’, and the problem only occurs when I use the query builder to narrow down the number of categories shown. We have several we wish to exclude (not empty). However, the drop down doesn’t actually show the categories I have specified, rather it lists categories twice, and the menu doesn’t work in any of the archive pages. They also aren’t appearing in alphabetical order. Surely this indicates there is an error in the query builder?

Just to be clear, I am NOT trying to create filters that can be combined in boleean style searches, we just want the links to point to the relvant archive pages, and to be able to specify which categories to include.

Looking at the way the first drop down behaves, there is clearly something wrong with the settings. I’d be grateful for any assistance!

[marc_a]

Hey @boera,

I suspect your issue is similar to this thread, please check our answers and let us know how it goes.

• WC sub-categories in "Terms (cloud)"

Hope that helps.

[boera]

I’m not sure my question was being understood here. In case anyone is reading this, I was able to resolve this by using ‘All terms’, then using conditions to remove the unwanted terms. All working perfectly now.

However, I’m a little confused as to how the query builder is supposed to work with the terms element. I’ve used query builders elsewhere to display one or two taxonomies, and thought I understood the functionality. However, in the terms element, I can’t get any kind of usable result using a query builder no matter what I try to achieve. Is it not possible to specify taxonomies with a query builder in the terms element?

[tristup]

Hi @boera,

We have understood your requirements and the problem, which is why I suggested you hire a developer who can assist you to do the customization or you can avail of our newly launched service called TOTAL CARE, where we offer small customizations.

Thanks

[boera]

Issue resolved using conditions, no customisation or developers needed. Never mind.

[tristup]

Hi @boera,

Glad to know that it is resolved now.

Thanks