Problem: I have a custom search View that includes 4 custom taxonomy filters. I would like to set one of the filters to a static value, so that all the results include one term from that custom taxonomy. Then I would like to use the relation "AND" to combine that with a group of 3 other custom taxonomy filters, which can be chosen on the front-end by the User, and combined using the "OR" relation. The combined effect should be like this graphic representation:
------------------------------------------------------
| Recipe Category (equal to "Shake") |
| |
| - AND - |
| |
| ____________________________________________ |
| | | |
| | Main Ingredient (set by URL parameter) | |
| | | |
| | - OR - | |
| | | |
| | Extra Ingredient (set by URL parameter) | |
| | | |
| | - OR - | |
| | | |
| | Fluid (set by URL parameter) | |
| -------------------------------------------- |
| |
-----------------------------------------------------
Solution: This type of combination of filters with nested AND/OR relations is not possible through the standard Views GUI, and requires a custom code solution. We offer the wpv_filter_query API that allows you to intercept the query and modify its tax_query details in real-time.
You can read more about complex or nested relations in taxonomy-based queries in the documentation linked below.
An example showing these APIs used together:
function tssupp_change_tax_query_and_or($view_args, $view_settings, $view_id)
{
$view_ids = array( 22575 ); // comma-separated list of View IDs where you want to apply this filter
$static_tax = 'recipe-category'; // the slug of the taxonomy that includes the static term "shake"
$static_term_id = 1084; // the term ID of "shake" in the static taxonomy "recipe-category"
/*
-- do not edit below this line --
*/
if ( in_array($view_id, $view_ids) ) {
// new tax query template
$new_tax_query = array(
array(
// code below will unshift selected front-end tax filters into this array
'relation' => 'OR',
),
array(
'taxonomy' => $static_tax,
'field' => 'id',
'terms' => array( $static_term_id ),
'operator' => 'IN',
'include_children' => 1,
),
'relation' => 'AND',
);
foreach ( $view_args['tax_query'] as $tax_query_term ) {
// loop over selected filters,
// verify is_array to skip 'relation' index,
// verify the slug of this tax is not
// same as the static taxonomy slug,
// unshift it into the new query's OR block
if( is_array($tax_query_term) && $tax_query_term['taxonomy'] != $static_tax ){
array_unshift( $new_tax_query[0], $tax_query_term );
}
}
// now overwrite the original tax_query with
// the new tax_query and you're done
$view_args['tax_query'] = $new_tax_query;
}
return $view_args;
}
add_filter('wpv_filter_query', 'tssupp_change_tax_query_and_or', 99, 3);
Up at the top, modify the View if necessary to customize it for your site. You may add other View IDs to the $view_ids array in comma-separated format if you have more than one View with similar filters where you want to apply this custom snippet. I copied the taxonomy slugs and term IDs from the debug information, so I'm pretty sure those are correct.
Add the code in your child theme's functions.php file, or in Toolset > Settings > Custom Code, and test it on the front-end of the site. Let me know the results and we can go from there.
Problem: I'm trying to create a conditional that tests whether or not a Term WYSIWYG field has content.
Solution: There is a known issue with special characters in conditional content, which can break conditionals. As a workaround, convert double-quotes to
& quot;
without the space, and convert single-quotes to
'
Our developers are working on a permanent solution to the problem.
We document known issues and their solutions in Toolset errata. Save time by checking there first and seeing if what you are facing is a known issue. This list is kept short. We do our best to resolve all known issues with every release of Toolset plugins.
Support Policy
Toolset staff will help you use the Toolset plugins correctly, provide any information you need, help troubleshoot problems and advice on best-practices.
Please make sure to issue only one topic per each support ticket.
