Fatals with 2.10.0

  • Resolved mtg169

    (@mtg169)


    1 week, 2 days ago

    Seeing the following fatal after updating to 2.10.0:

    Fatal error: Uncaught Error: Class "WebDecoy_AI_Referrals" not found in /srv/htdocs/wp-content/plugins/webdecoy/webdecoy.php:980
    Stack trace:
    #0 /srv/htdocs/wp-content/plugins/webdecoy/webdecoy.php(188): WebDecoy_Plugin->init_hooks()
    #1 /srv/htdocs/wp-content/plugins/webdecoy/webdecoy.php(177): WebDecoy_Plugin->__construct()
    #2 /srv/htdocs/wp-content/plugins/webdecoy/webdecoy.php(3525): WebDecoy_Plugin::instance()
    #3 /srv/htdocs/wp-content/plugins/webdecoy/webdecoy.php(3540): webdecoy()
    #4 /wordpress/core/7.1.2/wp-settings.php(597): include_once('/srv/htdocs/wp-...')
    #5 phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1374): require('/wordpress/core...')
    #6 phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1293): WP_CLI\Runner->load_wordpress()
    #7 phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start()
    #8 phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/bootstrap.php(84): WP_CLI\Bootstrap\LaunchRunner->process(Object(WP_CLI\Bootstrap\BootstrapState))
    #9 phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/wp-cli.php(35): WP_CLI\bootstrap()
    #10 phar:///usr/local/bin/wp-cli/php/boot-phar.php(20): include('phar:///usr/loc...')
    #11 /usr/local/bin/wp-cli(4): include('phar:///usr/loc...')
    #12 {main}
      thrown in /srv/htdocs/wp-content/plugins/webdecoy/webdecoy.php on line 980
Viewing 1 replies (of 1 total)
  • Plugin Author WebDecoy

    (@webdecoy1)

    1 week, 2 days ago

    Thanks for the report and the stack trace, and sorry about this. 2.10.0 called a class before the file that defines it was loaded, which caused a fatal error on every request, not only in WP-CLI. It’s fixed in 2.10.1, which is out now: wp plugin update webdecoy or update from the Plugins screen. We’ve also added a test that fails the build if this kind of load-order mistake comes back. Let me know if anything still looks off after updating.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.