Hide Empty Terms

By the way, in version 1.0.10 the Menu reads Ulitmate WPQSF, in case you haven’t noticed it yet.

I don’t understand. IF none of your cars is red, then searching the red in the car search form, should return no result found.

Note that taxonomies are actually independent from the cpt in the search form.
If you want to hide the red in the car search form, you might need to do it manually with a filter.
eg:

add_filter('uwpqsf_taxonomy_arg', 'exclude_terms_form','', 3);
function exclude_terms_form($args,$taxname,$formid){
   //if the car search form form id is 12345
   if($formid == '12345' && $taxname == 'color'){
         $args['exclude'] = '1,2,3,4';//the terms id you want to exclude
    }
   return $args;
}

You’re right, the search returns no results found. There’s nothing wrong with that.

My only issue is that the term “red” still shows in that taxonomy dropdown options, while I have the “Hide empty terms” option turned on.

Let me try to exemplify.

CPTs: Cars, Trucks, SUVs
Taxonomy: Color (shared by all the CPTs).

Car 1 – color = blue
Car 2 – color = grey
Car 3 – color = black

Truck 1 – color = red

When I go to the Car search form, my color dropdown options are:
– Blue
– Grey
– Black
– Red

If I chose the red option it will return no results.
But, since there are no red cars, shouldn’t that option be out of the dropdown options in the car search form?

Keep in mind that I don’t want to hide any specific term, I want to hide all the terms that have no results for that specific CPT.

Just like what I said, the taxonomy is independent from cpt. Hence you will see the red in every cpt.
There are few ways to do it, once is that I mentioned above , another one is exclude it in the filter setting page (exclude term id).
Another one is way more complicated and will cost you more db resource, which not recommended.

Ok, thanks a lot!

I guess I can use the filter above with a few modifications to make it dynamic.
I can check if a particular term is applied to a CPT and hide it if it’s not.

That’s the kind of approach that will cost me more db resource, since I have to cross-check every term with every CPT, right?

That’s the kind of approach that will cost me more db resource, since I have to cross-check every term with every CPT, right?

-Yes