Yes! I have deactivated the Yoast SEO plugin and can confirm I am no longer seeing the 404 errors on the network screen.
I am still getting some toolset warnings and errors in the PHP Error log when I open the editor for the page, and more errors appear if I leave the page open (eventually, I see a 500 error for wp-json in the network screen). These may be caused by a different issue. Should I start a new ticket?
Fatal error: Uncaught InvalidArgumentException: The classmap must be an array. in /home/site/public_html/wp-content/plugins/toolset-blocks/vendor/toolset/toolset-common/utility/autoloader.php:89
Notice: Trying to get property 'post_content' of non-object in /home/site/public_html/wp-content/plugins/toolset-blocks/backend/Services/ViewParsingService.php on line 310
Thanks for reporting the compatibility issue! I'll keep an eye out for that fix (and it may explain why my other sites with Toolset and Yoast have so many errors too!).
-Sarah
Hi Sarah,
I still have access to the website's admin area, but, I'll need the latest clone/snapshot of the website to investigate these errors on a different server.
Do I have your permission to download the latest clone/snapshot?
regards,
Waqar
Hi Waqar,
Awesome, thanks for creating this new ticket...and yes, please go ahead with troubleshooting the site when you have time.
I just tested it again, opened first the "All Products test" page and no errors were logged in the PHP Error Log on the site Dashboard.
Then I opened the "All Products" page, and again I am getting a bunch of errors and the dreaded "There has been a critical error on this website." notice.
Now both versions of the page are triggering errors (I think the content should be the same on both draft test and published non-test), and I also see 500 errors in Network but I guess that is due to server timeout from whatever is triggering all the error log activity.
Just to test, I opened a few pages with no Toolset blocks, and they loaded without any issues. Then I opened a page ("Test Page") with just a Toolset dynamic image, no Views, and it was also error-free. So, it appears that only opening pages with Views/Content Templates, and the Content Templates themselves ("Product Template" and "Features Products for Home Page") are triggering a slew of errors.
Here are some more of the Toolset errors:
Fatal error: Uncaught Error: Call to undefined function OTGS\Installer\FP\partial() in /home/site/public_html/wp-content/plugins/types/vendor/otgs/installer/includes/admin-notices/notices/Hooks.php:16
Fatal error: require_once(): Failed opening required '/home/fadedquill/public_html/wp-content/plugins/toolset-blocks/embedded/inc/filters/wpv-filter-category-embedded.php' (include_path='.:/opt/alt/php74/usr/share/pear') in /home/site/public_html/wp-content/plugins/toolset-blocks/loader.php on line 223
Fatal error: Uncaught Error: Class 'WPV_Shortcode_Post_Field_Iterator_GUI' not found in /home/site/public_html/wp-content/plugins/toolset-blocks/application/models/shortcode/factory.php:131
...along with many more errors for other plugins too, so I don't know which of these errors tells us what is going on, and which are just a side effect of a deeper problem. For the most part, the errors look different each time.
I can confirm that Yoast SEO and Jetpack are currently deactivated.
Let me know if there's anything else I can do on my end.
-Sarah
Thank you for this update.
I downloaded a fresh clone from your website and even though I can see the errors when trying to edit the "All Products" page on your website, I couldn't reproduce this on that clone.
This makes me believe that something specific to your website's server/hosting environment is involved. These remaining errors indicate that some of the files or codes are missing/unavailable, even though they are not.
I suspect that somehow server is terminating the connection before all the necessary processing has been completed, which results in these errors.
I'll recommend testing out your website's clone on any other online or localhost server as well. Once, it is confirmed that this is indeed related to the server, you can take up this matter with the host and switch to a different one if needed.
The Toolset's recommended server requirements are available at:
https://toolset.com/toolset-requirements/
