Home › Toolset Professional Support › [Assigned] High Number of wpv_get_archive_query_results messages
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
This topic contains 2 replies, has 1 voice.
Last updated by Focus on the Family 19 hours, 43 minutes ago.
Assisted by: Christopher Amirian.
We are experiencing an issue with our hosting web server being heavily impacted by a high number of wpv_get_archive_query_results messages hitting the admin-ajax function. These appear to be coming from the Toolset Views plugin used on several of our sites. This is slowing down all of our websites on the server. Is there any way to reduce or eliminate all these calls from happening?
Barney Royalty
Focus on the Family
Hi Barney Royalty,
Welcome to Toolset support. It is hard to know why might be the reason for the multiple call of the function.
It may be the fact that the website is too big or there are other scenarios that needs to be checked
I suggest that you follow the steps below:
1. Check if the same thing happens if you use Toolset in isolation.
- IMPORTANT STEP! Create a backup of your website. Or better approach will be to test this on a copy/staging version of the website to avoid any disruption of a live website.
- Switch to the default theme such as "TwentyTwenty" by going to "WordPress Dashboard > Appearance > themes".
- Go to "WordPress Dashboard > Plugins" and deactivate all plugins except Toolset and its add-ons.
- Check if you can still recreate the issue.
- If not, re-activate your plugins one by one and check the issue each time to find out the plugin that causes the problem.
2. Make sure all Toolset plugins are updated.
I see that you use some older versions of Toolset. Please update them.
- IMPORTANT STEP! Create a backup of your website. Or better approach will be to test this on a copy/staging version of the website to avoid any disruption of a live website.
- Go to "WordPress Dashboard > Plugins > Add new > Commercial (tab)".
- Click the "Check for Updates" button.
- Update Toolset and its addons there.
3. Pinpoint a view that might has the issue
Remove all the views you used on your website and keep only one and test, do for the other views to know if there is any specific view that is a source of the issue or not.
Check the view and see if there are any custom coding used there and test to see how many items of a post type or taxonomy the view runs on. Maybe the issue is that you have a very big amount of content there and you'd better use some sort of pagination or caching.
Thanks.
Here is an example of what we're currently seeing on our Plugged In website:
----------------------------------------------------------------------------------------------------------------
/nas/content/live/pluggedinprod/wp-content/plugins/wp-views/embedded/inc/wpv-pagination-embedded.php
1720: || $_REQUEST['action'] == 'wpv_get_archive_query_results'
2639: && $_REQUEST['action'] == 'wpv_get_archive_query_results'
2743: || $_REQUEST['action'] == 'wpv_get_archive_query_results'
/nas/content/live/pluggedinprod/wp-content/plugins/wp-views/embedded/inc/wpv-shortcodes.php
622: || $_REQUEST['action'] == 'wpv_get_archive_query_results'
1070: || $_REQUEST['action'] == 'wpv_get_archive_query_results'
1226: || $_REQUEST['action'] == 'wpv_get_archive_query_results'
1533: || $_REQUEST['action'] == 'wpv_get_archive_query_results'
1945: || $_REQUEST['action'] == 'wpv_get_archive_query_results'
/nas/content/live/pluggedinprod/wp-content/plugins/wp-views/embedded/inc/wpv-archive-loop.php
142: add_action( 'wp_ajax_wpv_get_archive_query_results', array( $this, 'wpv_get_archive_query_results' ) );
143: add_action( 'wp_ajax_nopriv_wpv_get_archive_query_results', array( $this, 'wpv_get_archive_query_results' ) );
1869: function wpv_get_archive_query_results() {
2102: && $_REQUEST['action'] == 'wpv_get_archive_query_results'
/nas/content/live/pluggedinprod/wp-content/plugins/wp-views/embedded/inc/wpv.class.php
375: || $_REQUEST['action'] == 'wpv_get_archive_query_results'
432: || $_REQUEST['action'] == 'wpv_get_archive_query_results'
749: || $_REQUEST['action'] == 'wpv_get_archive_query_results'
/nas/content/live/pluggedinprod/wp-content/plugins/wp-views/vendor/toolset/toolset-common/utility/utils.php
65: 'wpv_get_archive_query_results',
/nas/content/live/pluggedinprod/wp-content/plugins/wp-views/vendor/toolset/toolset-common/user-editors/editor/screen/divi/frontend.php
53: $load_requests['action'][] = 'wpv_get_archive_query_results';
/nas/content/live/pluggedinprod/wp-content/plugins/wp-views/vendor/toolset/divi/includes/extension.php
80: || $_REQUEST['action'] == 'wpv_get_archive_query_results'
/nas/content/live/pluggedinprod/wp-content/plugins/wp-views/application/models/WooCommerce/WcQuery.php
122: [ 'wpv_get_view_query_results', 'wpv_get_archive_query_results' ],
/nas/content/live/pluggedinprod/wp-content/plugins/wp-views/application/controllers/compatibility/wpa-block-editor/wpa-block-editor.php
1275: [ 'wpv_get_view_query_results', 'wpv_get_archive_query_results' ],
/nas/content/live/pluggedinprod/wp-content/plugins/wp-views/backend/Services/WPMLService.php
42: [ 'wpv_get_view_query_results', 'wpv_get_archive_query_results' ],
/nas/content/live/pluggedinprod/wp-content/plugins/types/vendor/toolset/toolset-common/utility/utils.php
65: 'wpv_get_archive_query_results',
/nas/content/live/pluggedinprod/wp-content/plugins/types/vendor/toolset/toolset-common/user-editors/editor/screen/divi/frontend.php
53: $load_requests['action'][] = 'wpv_get_archive_query_results';
/nas/content/live/pluggedinprod/wp-content/plugins/types/application/models/field/abstract.php
89: || $_REQUEST['action'] === 'wpv_get_archive_query_results'
----------------------------------------------------------------------------------------------------------------------------
I've set up a sandbox copy of the site. Would it be helpful in your investigation to be able to access it?