Thank you for contacting us and I'll be happy to assist.
To better understand how the search filters are set, I'll need access to the page itself.
Can you please share temporary admin and front-end access to your site, so that I can log in and see how the page is set up?
( preferably to a test/development site, if possible )
Your next answer will be private which means only you and our support team will have access to it.
Note: Please backup your database and website before sharing the access information.
For example, for your view with ID "112", you can add the following code in your active theme's "functions.php" file:
add_filter( 'wpv_filter_query', 'filter_view_query_fn', 1000 , 3 );
function filter_view_query_fn( $query_args, $view_settings ) {
// code to limit this function only for a view with specific ID
if ( !is_admin() && ( isset($view_settings['view_id']) && $view_settings['view_id'] == 112) ) {
// view the current query
echo '<pre>';
print_r($query_args);
echo '</pre>';
// view the parameter's passed through the filters
echo '<pre>';
print_r($_GET);
echo '</pre>';
// add code to change the query parameters, as needed
}
return $query_args;
}
Feel free to adjust the above code as needed and for a more personalized assistance around custom programming, you can consider hiring someone from our list of recommended contractors: https://toolset.com/contractors/
I hope this helps and please let me know if you have any question around this.
I contacted a contractor, but it seems he is not interested...
Your code adjusted a little bit:
add_filter( 'wpv_filter_query', 'filter_view_query_fn', 1000 , 3 );
function filter_view_query_fn( $query_args, $view_settings ) {
// code to limit this function only for a view with specific ID
if ( !is_admin() && ( isset($view_settings['view_id']) && $view_settings['view_id'] == 112) ) {
/*
// view the current query
echo '<pre>';
print_r($query_args);
echo '</pre>';
// view the parameter's passed through the filters
echo '<pre>';
print_r($_GET);
echo '</pre>';
*/
// add code to change the query parameters, as needed
if ($_GET['wpv-wpcf-blend'] == 1) {
// change query , so it does not search in wpcf-variety , but in (wpcf-variety-member1 OR wpcf-variety-member2 OR ... OR wpcf-variety-member7)
}
}
return $query_args;
}
Based on what you've shared, my understanding is that the role of "Ποικιλία" filter is to provide users to select a value to compare for the other "variety-member" custom fields (1-7).
Your code works as expected only the first time. All subsequent searches give no results.
You can try it on the site to see what I mean. Whenever $_GET['wpv-wpcf-blend'] == 1, the search gives results only once.
To reproduce, from menu go to "Αναζήτηση ελαιολάδων" ie /oliveoils-finder/
There, for Blend you check "Ναι" (which is Yes) and from "Ποικιλία" you choose "Κορωνέικη (...)" which is 6th from top.
Then you press the button to do the search. This will search all olive oil categories ("Κατηγορία") which are Blends, with one component of a Κορωνέικη variety.
This search is fine and results are shown in /oliveoils-found/?... page, which includes the search form.
From there, all subsequent searches for Blends that include a "Ποικιλία", give no results ("Δεν βρέθηκε τίποτα").
For example, if Blend is "Ναι" and "Ποικιλία" is "Μαστοειδής η κοινή(...)" (11th from top), there are no results, although it exists such a blend. To verify, start a new search by loading /oliveoils-finder/ page. Above settings give 1 result.
I noticed that your view is set to update the search results, with AJAX.
( screenshot: hidden link )
If you'll set the search settings to "Reload the page to update the View results", the custom query filter function will work, as expected.
To make this function work with AJAX results, advance custom code/script changes will be needed to adjust the AJAX calls, which I'm afraid, is beyond the scope of support that we can provide.
