I deactivated the Google plugin to enable the toolset debug setting but it doesn't seem to be working. So after enabling the WordPress debug setting, I was given the text below...
Is this what you need?
Fatal error: Uncaught TypeError: Argument 1 passed to Google\Site_Kit\Core\REST_API\REST_Routes::register_routes() must be an instance of WP_REST_Server, string given, called in /var/www/html/wp-content/plugins/google-site-kit/includes/Core/REST_API/REST_Routes.php on line 92 and defined in /var/www/html/wp-content/plugins/google-site-kit/includes/Core/REST_API/REST_Routes.php:104 Stack trace: #0 /var/www/html/wp-content/plugins/google-site-kit/includes/Core/REST_API/REST_Routes.php(92): Google\Site_Kit\Core\REST_API\REST_Routes->register_routes('') #1 /var/www/html/wp-includes/class-wp-hook.php(288): Google\Site_Kit\Core\REST_API\REST_Routes->Google\Site_Kit\Core\REST_API\{closure}('') #2 /var/www/html/wp-includes/class-wp-hook.php(312): WP_Hook->apply_filters(NULL, Array) #3 /var/www/html/wp-includes/plugin.php(478): WP_Hook->do_action(Array) #4 /var/www/html/wp-content/plugins/wp-views/vendor/toolset/common-es/php/Block/Style/Responsive/ToolsetSettings.php(28): do_action('rest_api_init') #5 /var/www/html/wp-includes/cl in /var/www/html/wp-content/plugins/google-site-kit/includes/Core/REST_API/REST_Routes.php on line 104
There has been a critical error on your website. Please check your site admin email inbox for instructions.
From what I see here the Google plugin is throwing a fatal error.
I would recommend contacting the support for this team due to the error here
Fatal error: Uncaught TypeError: Argument 1 passed to Google\Site_Kit\Core\REST_API\REST_Routes::register_routes() must be an instance of WP_REST_Server, string given, called in /var/www/html/wp-content/plugins/google-site-kit/includes/Core/REST_API/REST_Routes.php on line 92
I suspect that this will not only interfere with our plugins but others as well so I would recommend disabling and then contact the google support for a resolution for this since the issue in on the side of the Google Plugin.
I think it might be due to Toolsets integration with Google. This is only an issue with the Toolset plugin settings everything else works fine for the websites and all other plugins. I don't think Google will be inclined to adjust their plugin to fit the needs of the Toolset plugin.
I can work around it by deactivating and reactivating the plugin when I need access to the Toolset plugin settings, but I think this needs to be investigated a bit more and possibly adjusted on the Toolset side because Google more than likely won't fix something that is only affecting the Toolset plugin.