PHP Fatal error 12.3

Same issue here, any luck?

We are experiencing similar issues.

An error of type E_ERROR was caused in line 115 of the file /nas/content/live/website-name/wp-content/plugins/wordpress-seo/admin/class-admin.php. Error message: Uncaught Error: Class ‘WPSEO_Admin_Settings_Changed_Listener’ not found in /nas/content/live/website-name/wp-content/plugins/wordpress-seo/admin/class-admin.php:115
Stack trace:
#0 /nas/content/live/website-name/wp-content/plugins/wordpress-seo/admin/class-admin-init.php(31): WPSEO_Admin->__construct()
#1 /nas/content/live/website-name/wp-content/plugins/wordpress-seo/wp-seo-main.php(421): WPSEO_Admin_Init->__construct()
#2 [internal function]: wpseo_admin_init(”)
#3 /nas/content/live/website-name/wp-includes/class-wp-hook.php(286): call_user_func_array(‘wpseo_admin_ini…’, Array)
#4 /nas/content/live/website-name/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array)
#5 /nas/content/live/website-name/wp-includes/plugin.php(465): WP_Hook->do_action(Array)
#6 /nas/content/live/website-name/wp-settings.php(394): do_action(‘plugins_loaded’)
#7 /nas/content/live/website-name/wp-config.php(120): require_once(‘/nas/content/li…’)
#8 /nas/content/live/website-name/wp-load.php(37): require_once(‘/nas/content/li…’)
#9 /nas/content/

same error

Can everybody please contribute to https://github.com/Yoast/wordpress-seo/issues/13680 to help find this thing and fix it?

Thank you.

Is anyone still having this problem? Someone suggest it might be opcode caching, so clear and see what happens (use opcache_reset();).

@inndesign,

We apologize for the difficulties you are having with the plugin. If you are still experiencing the issue, we would like some more information.

1. Can you confirm you are using WordPress 5.2.4? You can check by clicking on the W in the top left and selecting About. If you need to update, please check with your host provider.?Please know that if you are using an older version of WordPress Core you may experience unexpected behavior with Yoast.?This guide explains more:?https://yoast.com/why-we-dont-support-old-wordpress-versions/.

2. Are all your non-Yoast plugins and themes also updated?

3. Does clearing your caching from your theme, plugin, server, CDN like CloudFlare or browser resolve the issue? If you are not sure how to clear caching from theme/plugin please speak to those authors. If you want to clear cache from the server, please speak to your host provider. To clear the cache from a browser use this guide: https://kb.yoast.com/kb/how-to-clear-my-browsers-cache/.

@cosmoweb @run-lil-lu-run @anjoid

If you are still experiencing the issue per the forum guidelines, we ask that you please create separate topics for the issues you are experiencing. That way it’s easier to track issues and provide assistance on your specific concerns on your specific site. Plus, you will get your own alerts for the issue rather than someone else’s. Thanks!

Wordpress version 5.2.4 used.
All plugins updated.
Don’t use caching or CDN.
Thanks.

@inndesign This is most commonly caused by server cache, typically opcache, which your webhost may be using even if you didn’t install a caching plugin within WordPress. Please ask your webhost to clear all server cache.

If server cache has been cleared, please manually install the plugin via SFTP / FTP by following the steps found here:?How can I manually update my plugin?

This will ensure that all of the files are successfully updated.

Our dedicated LAMP server does not include Zend OpCache as an installation. Nor is there caching in cPanel by default. Visually checking, there is no var/cache/ directory on any account.

Are you still getting the error? If so, do you know what triggers it?

My account errors have subsided. Could have been anything, but nothing new regarding the original post. Thanks.

@inndesign Thanks for confirming that the error is no longer occurring. We are going ahead and marking this issue as resolved. If you require any further assistance please create a new issue.

The Github page has marked the issue resolved. And this thread as well. However, I just got this error as well. Am I hearing right: a cache clear and then manual install of the plugin is the proposed solution?