This hook below is able to filter out the returned list and you can essentially tell the filter what terms are to be available on the frontend for filtering.
Thank. Ok so I guess I would need something like this as suggested on the Toolset site:
// Following example limits the terms offered in the frontend filter to those which slug is either cat-one or cat-three.
add_filter( 'wpv_filter_taxonomy_frontend_search_get_terms_args', 'prefix_modify_get_terms_args', 10, 3 );
In your case you will need to add this to your Toolset Custom code section at Toolset->Settings-> Custom Code and activate it.
// Following example limits the terms offered in the frontend filter to those which slug is either cat-one or cat-three.
add_filter( 'wpv_filter_taxonomy_frontend_search_get_terms_args', 'prefix_modify_get_terms_args', 10, 3 );
function prefix_modify_get_terms_args( $args, $taxonomy, $view_id ) {
if($view_id == 1234 && $taxonomy == 'tax_slug')
$args['slug'] = array(
'cat-one',
'cat-three',
);
return $args;
}
Now replace 1234 with the ID of your view, 'tax_slug' with the slug of the taxonomy that is displayed on the filter and in the array you will add all the terms that you want to be available for this filter.
This should then only give you those terms on the frontend filter.
I see one issue with how you've added the code, you didn't "tax_slug" to the slug of the taxonomy that the filter is displaying.
Trying changing this to the correct slug. If this doesn't work would you mind allowing me to have access to this setup on your staging environment to better adapt the code to your specific filter.
I've enable the private fields for your next response should this be needed.