Error 500 after Extension Manager Update

  • Resolved cebln

    (@cebln)


    3 years ago

    [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.

    • This topic was modified 3 years ago by cebln. Reason: more info
    • This topic was modified 3 years ago by cebln.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Sybre Waaijer

    (@cybr)

    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!

    Thread Starter cebln

    (@cebln)

    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.

    • This reply was modified 3 years ago by cebln.
    Thread Starter cebln

    (@cebln)

    Found the problem. Nothing wrong with PEAR. See my message.

    You actually did not have a chance to find the problem yourself, because the issue (uppercase chars in the original path vs. a require of a lowercase path) was in the first part of the path that I shortened in this bug report for security reasons. ??

    Thread Starter cebln

    (@cebln)

    Solved with the latest update the same day. That was fast!

    Plugin Author Sybre Waaijer

    (@cybr)

    Thanks again for debugging ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Error 500 after Extension Manager Update’ is closed to new replies.