Problem: I have a custom search View that uses a distance filter and a taxonomy filter, but the taxonomy filter does not seem to work correctly.
Solution: Check your View's Query Filter configurations. In this case the url_param was set incorrectly and should be changed to "wpvexpertcategory" as shown here:
Problem: I have a View with several checkbox filters. If a User clicks the checkboxes quickly, sometimes the checkboxes begin to flicker and disappear unexpectedly.
Solution: In the View's custom search settings, choose the option "Let me choose individual settings manually", then select "Always show all inputs" and "Update the View results only when clicking the search button."
The issue here is that the user has a taxonomy with child terms but they wanted to have a separate filter for child and Parent terms.
Solution:
Unfortunately no this isn't possible with our toolset plugins as we display all the the taxonomies regardless if they are Parent/Child.
What I do recommend is that you can separate your Parent and use a separate taxonomy for the children. Doing this you can then introduce a secondary filter will the children and the children will filter based on what you selected in the parent .
The problem here is that the customer wanted to automatically delete certain posts where a specific status has been assigned.
Solution:
Unfortunately this is something that would require some amount of custom coding to achieve. Unfortunately such custom coding is out of the scope of our support forum and as such I would recommend contacting one of our certified consultants to achieve this.
Problem: I have a View placed near the bottom of a web page. When a user chooses filters and submits a search, the page reloads and the search results are displayed. However, the page returns to the top and the search results are not visible in the window. I want to return to the area where the search results are visible. For other reasons I cannot use AJAX to update the results here.
Solution: Add a unique ID to an HTML element in your search form. Use JavaScript to detect the unique URL parameter wpv_view_count applied by this form when search is submitted. When the URL parameter is present and the value matches this form, use JavaScript to update location.hash with the unique ID you just created. The page will jump to place.
var QueryString = function () {
// This function is anonymous, is executed immediately and
// the return value is assigned to QueryString!
var query_string = {};
var query = window.location.search.substring(1);
var vars = query.split("&");
for (var i=0;i<vars.length;i++) {
var pair = vars[i].split("=");
// If first entry with this name
if (typeof query_string[pair[0]] === "undefined") {
query_string[pair[0]] = decodeURIComponent(pair[1]);
// If second entry with this name
} else if (typeof query_string[pair[0]] === "string") {
var arr = [ query_string[pair[0]],decodeURIComponent(pair[1]) ];
query_string[pair[0]] = arr;
// If third or later entry with this name
} else {
query_string[pair[0]].push(decodeURIComponent(pair[1]));
}
}
return query_string;
}();
if(QueryString.wpv_view_count && QueryString.wpv_view_count == "772-TCPID4") {
location.hash = "#hash";
}
Change "772-TCPID4" to match the value generated by your form. Change "#hash" to match your unique ID.
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.
