I received your email with the follow-up questions, but overlooked replying to it later. Sorry about that, it's one of the perils of communicating off-forum, because I have a queue of forum tickets to attend to which is how I can see what I have outstanding that needs replying to.
If you have something sensitive to share with me you can drop me an email, but it would be useful to post a brief comment in the forum so that it appears in my list of ongoing tickets needing a reply.
So, to the questions themselves. I'll come back to the issue of the CSS styling, let's get the filters working first.
There are two main issues here.
One is that the custom shortcode I coded was setup to work with one region taxonomy (Indiana States), and now that you have it working you want to be able to use replicate it to work with 50+ taxonomies. (Note that you register the shortcodes to be able to use them inside Views shortcodes, as you do when you use them as a shortcode attribute inside your wpv-view shortcode. You don't need to register them as functions for conditional shortcodes.)
The second, reported here in your previous post, is that the taxonomy filter needs to be of the form product AND (region1 OR region2 OR region3 etc.), but when you add the filters to the view you only have the options of AND all taxonomy filters or OR any of the taxonomy filters.
This last point is a limitation of Views, you cannot construct more complex taxonomy queries, although it is something WordPress is capable of: see Nested Taxonomy Handling under https://codex.wordpress.org/Class_Reference/WP_Query#Taxonomy_Parameters
To get round this there are 2 choices. One is to change the product taxonomy to use custom fields instead. You can then have a filter for the product as a custom field, and then all of your region taxonomy filters with an OR relation.
If changing the product taxonomy to a custom field is unappealing then we are left with using the Views API and manually coding the taxonomy query to rewrite it in the required more complex form.
From the debug info, here we can see the tax_query part of the relevant query when we visit the AMI product page, for example:
[tax_query] => Array
(
[0] => Array
(
[taxonomy] => alabama-county
[field] => id
[terms] => Array
(
[0] => 432
)
[operator] => IN
[include_children] => 1
)
[1] => Array
(
[taxonomy] => indiana-county
[field] => id
[terms] => Array
(
[0] => 366
[1] => 1089
[2] => 1203
[3] => 1330
[4] => 1880
[5] => 1898
[6] => 2161
[7] => 2437
[8] => 3065
[9] => 3317
)
[operator] => IN
[include_children] => 1
)
[2] => Array
(
[taxonomy] => new-mexico-county
[field] => id
[terms] => Array
(
[0] => 522
)
[operator] => IN
[include_children] => 1
)
[3] => Array
(
[taxonomy] => product-list
[field] => id
[terms] => Array
(
[0] => 3656
)
[operator] => IN
[include_children] => 1
)
[relation] => AND
)
We would need to modify that tax_query to bundle all the non-product-list taxonomies into a nested array with an OR relation.
I am going to work on that now and see if I can come up with something.
Also, with the custom shortcode I wrote, it specifically checks for the indiana-county taxonomy.
Rather than register 50+ custom shortcodes I can modify it so that you pass the taxonomy you are using as a shortcode attribute, so you can re-use the same custom shortcode for all of the region taxonomies.
Shall I do that, too?
