Fatal errors occurred today caused by this plugin

  • Resolved radgh

    (@radgh)


    11 months, 1 week ago

    A client’s website was down today. I found an error in the PHP log as the cause and disabling the plugin by renaming the folder with SFTP, which fixed the issue.

    The error in the log, repeated many times, was:

    PHP Fatal error: Uncaught Error: Call to undefined method Composer\Autoload\ClassLoader::setClassMapAuthoritative() in /www/wp-content/plugins/bunnycdn/vendor/composer/autoload_real.php

    I updated the plugin through the WordPress backend while it was disabled. I still receive a fatal error when trying to activate or delete the plugin:

    Deletion failed: There has been a critical error on this website.

Uncaught Error: Call to undefined method Composer\Autoload\ClassLoader::setClassMapAuthoritative() in /www/wp-content/plugins/bunnycdn/vendor/composer/autoload_real.php:34 

Stack trace: 
#0 /www/wp-content/plugins/bunnycdn/vendor/autoload.php(25): ComposerAutoloaderInit117c57de7ba909752bac22364ccff41b::getLoader() 
#1 /www/wp-content/plugins/bunnycdn/bunnycdn.php(52): require_once('/www/wp-content…') 
#2 /wordpress/wp-includes/class-wp-hook.php(324): bunnycdn_uninstall_plugin('') 
...

    I deleted the plugin entirely using SFTP, the installed it again from the plugin screen. It still gives a fatal error warning. Is there a fix?

    Plugin version 2.1.1
    WordPress version 6.4.3
    PHP version 8.2

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author bunny.net

    (@bunnycdn)

    This sounds like an issue with multiple plugins in your WordPress using different versions of composer. I could not reproduce issue, but I did some changes that might have fixed it. Please try again with the 2.1.3 version released today.

    Thread Starter radgh

    (@radgh)

    Thanks for the update! The issue relating to Composer makes sense and I hadn’t thought of that. We have a few old plugins that no longer get updated on this site, so that was probably the issue.

    However after updating today, the problem has gone away. For some reason I had to reconfigure the plugin, but that was easy.

    All is good now. Thank you!!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Fatal errors occurred today caused by this plugin’ is closed to new replies.