Error 500 after Extension Manager Update
-
[08-Nov-2021 09:10:40 UTC] PHP Fatal error: require(): Failed opening required ‘…./plugins/the-seo-framework-extension-manager/extensions/essentials/articles/trunk/inc/classes/front.class.php’ (include_path=’.:/usr/share/pear:/usr/share/php’) in /plugins/the-seo-framework-extension-manager/inc/classes/core.class.php on line 1183
This is not related to security plugins such as iThemes and NinjaFirewall, it happens also with those switched off and start as soon as the ARTICLES module is activated in the extension manager.
-
Hello!
Thank you for raising this issue.
The Pear autoloader is included in some other plugins, such as BackupWP (known from a report sent to us privately). The autoloader is too lenient loading files, causing errors. There seems to be an ongoing wave of reports with various plugins facing this issue; it’s not isolated to Extension Manager.
Often this issue is only apparent after updating a plugin. This is because the plugin load order can change due to an update, so the autoloaders changed order.
Could you please try deactivating other plugins one by one, and see if the error reoccurs? This should help find the issue. Please report the plugin that causes this, so we can work on a solution. Thank you!
Hi, the problem persisted after all plugins were deactivated (besides SEO Framewrk + Extension manager).
Our provider has this path for PEAR
include_path = "/pear-installationsverzeichnis/PEAR:.:/usr/local/lib/php"
https://www.df.eu/de/support/df-faq/webhosting/skriptsprachen/pear/If necessary, I can open a support request at the provider, regarding this required path and how to use this in a WordPress module.
- The topic ‘Error 500 after Extension Manager Update’ is closed to new replies.
