Plugin Support
Jerlyn
(@jerparx)
Hi @escitsupport
Sorry to hear about the issue you are having. Can you please confirm if you are running the latest WordPress (5.1) and Yoast SEO 9.7?
If you update them, does the issue resolve?
I have this exact same error and can confirm I’m on the latest wordpress (5.1) and I removed the plugin from wp-content/plugins and re-installed it through the plugin install interface. As soon as the plugin was installed I got the exact same error.
Confirming the same issue; WP 5.1, Yoast 9.7
Updated the WP install and the plugin a several days ago, and everything was working fine. Then last Friday I abruptly started getting a 500 in the admin area.
The error is: PHP Fatal error: Uncaught Error: Class ‘WPSEO_MyYoast_Proxy’ not found in /[redacted]/wp-content/plugins/wordpress-seo/admin/class-admin.php:113
Disabling the plugin eliminates the error. However, we need to be able to use the plugin.
Although this is likely unrelated, I will mention that I first noticed the error after pushing a testing file to the server (containing a call to phpinfo()). However, even after removing that file I still get a 500 error when I enable Yoast
We noticed the error when upgrading one of our client’s plugin to the latest version.
Details of the clients setup is:
WooCommerce version: 3.5.5
WordPress version: 5.0.3 – There is a newer version of WordPress available (5.1)
WordPress multisite: –
WordPress memory limit: 512 MB
Hi, @escitsupport
We are not sure why that is happening though that sounds like a plugin or theme conflict. Can you try and gather as much information for us as possible? Please perform the following:
1. Make sure you are using the most recent version of Yoast, v9.7 (we are not sure what exact version you have).
2. Make sure that all your non-Yoast plugins and themes are updated.
3. Make sure the issue doesn’t persist when Yoast SEO is disabled.
4. Check for conflicts.
If you didn’t find any conflicts or errors, we think the issue is specific to your site. We’d need to investigate further but are unable to do so on these forums. You can purchase Yoast SEO Premium and receive our Premium email support and we can help you further.
@travstone, @arcterex
We ask that you please try the steps above and if the issue continues to happen please create a new topic. That way we can address the issue happening on your specific environment in your own topic. It also helps us to better manage multiple issues.
All plugins were updated and Yoast was the last to be updated (given that it was in A-Z order)
As soon as the Yoast plugin was updated, that was the point it crashed the admin side. Version 9.7
I cannot reactivate due to the crashing.
@escitsupport The error may be being caused due to an issue with the update not completing successfully. If you manually update the plugin to version 9.7 does this resolve the error? We have instructions on how to upgrade the plugin manually at the following link: https://kb.yoast.com/kb/how-can-i-update-my-free-plugin/#ftp. You will need an FTP program such as FileZilla and your FTP details, which can be obtained from your host provider.
I experienced the very same problem. It looks like it was caused by PHP opcache being enabled. After force-expiring the cache, the crash disappeared and the WP Admin panel showed up as expected.
Plugin Support
Jerlyn
(@jerparx)
@escitsupport Can you please confirm if the same fix applies to your site? Does clearing your cache resolve the issue?
I did experience similar behavior on couple website. It was related to OPcache and specific settings (eg. opcache.validate_timestamps is 0 or opcache.revalidate_freq is greater than couple seconds). You could install plugin WP OPcache which could help in some case (also this plugin adds button for manual clear OPcache).
Related WP core ticket: https://core.trac.wordpress.org/ticket/36455
Yoast SEO has the code which runs opcache_reset(), but it seems that it doesn’t work in all cases.
Was about to try the manual update, but I noticed v10 is out today… updated via the admin and this seems to have worked fine, although 9.7 did for a few days as well… will post back if things change
Thanks for confirming that updating the plugin to version 10.0 corrected the issue. Please let us know if you experience any further issues though.
We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.
