1) Setup a post view, query posts, without any filter.
2) use "wpv_filter_query" to trigger a custom PHP function, in this PHP function, use your custom SQL query to get those specific post IDs, then pass the value as parameter "post__in" of query
Problem:
When you have Select2 inputs in a Toolset form (e.g. parent post selectors in a one-to-many relationship, where the form applies to the child post), and use the TAB key to move through the form on the front-end, then selecting an option in the Select2 inputs will provoke the next TAB click to reset the current location.
This means after selecting the option in Select2, pressing TAB will not lead to the next input but back to the top of the page.
What best way can you suggest to debug/troubleshoot query performance for a View? What can I look into or do to see why some of my Views are taking 15 seconds to run. Our Posts database is just over 3,700 posts so it shouldn't be data volume. But could be something I am doing. For most of my views, I use the Query Filter and then within the loop I have IF statements to filter out more records from the view. For some complex Queries that can't be done via the QUery Filter, I'm using the wpv_filter_query FILTER.
Is it recommended that for a dynamic web application, we set the cached attribute to off (cached="off") or can we leave it on to gain performance? Will record updates be reflected immediately on the views or retrieve cached data?
Solution:
You can set the cached attribute to on by removing attribute cached="off", it will gain performance.
The record updates will be reflected immediately on the views in most cases.
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.
