Kadence Blocks breaks WP-CLI plugin updates

  • Resolved Austin Ginder

    (@austinginder)


    9 months ago

    This issue doesn’t seem tied to a particular version of Kadence Blocks. I’ve seen it happen on versions 3.2.25, 3.2.23, 3.2.22, 3.2.21, 3.2.19, 3.2.17 and others. When running WordPress plugin updates over WP-CLI wp plugin update --all the following PHP fatal happens:

    PHP Fatal error:  Uncaught TypeError: KadenceWP\KadenceBlocks\StellarWP\Uplink\Admin\Package_Handler::filter_upgrader_pre_download(): Argument #2 ($package) must be of type string, null given, called in /wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/stellarwp/uplink/src/Uplink/Admin/Provider.php on line 171 and defined in /wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/stellarwp/uplink/src/Uplink/Admin/Package_Handler.php:33
Stack trace:
#0 /wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/stellarwp/uplink/src/Uplink/Admin/Provider.php(171): KadenceWP\KadenceBlocks\StellarWP\Uplink\Admin\Package_Handler->filter_upgrader_pre_download(false, NULL, Object(Plugin_Upgrader), Array)
#1 /wp-includes/class-wp-hook.php(324): KadenceWP\KadenceBlocks\StellarWP\Uplink\Admin\Provider->filter_upgrader_pre_download(false, NULL, Object(Plugin_Upgrader), Array)
#2 /wp-includes/plugin.php(205): WP_Hook->apply_filters(false, Array)
#3 /wp-admin/includes/class-wp-upgrader.php(318): apply_filters('upgrader_pre_do...', false, NULL, Object(Plugin_Upgrader), Array)
#4 /wp-admin/includes/class-wp-upgrader.php(827): WP_Upgrader->download_package(NULL, true, Array)
#5 /wp-admin/includes/class-plugin-upgrader.php(392): WP_Upgrader->run(Array)
#6 phar:///usr/local/bin/wp/vendor/wp-cli/extension-command/src/WP_CLI/CommandWithUpgrade.php(445): Plugin_Upgrader->bulk_upgrade(Array)
#7 phar:///usr/local/bin/wp/vendor/wp-cli/extension-command/src/Plugin_Command.php(700): WP_CLI\CommandWithUpgrade->update_many(Array, Array)
#8 [internal function]: Plugin_Command->update(Array, Array)
#9 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(100): call_user_func(Array, Array, Array)
#10 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}(Array, Array)
#11 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(497): call_user_func(Object(Closure), Array, Array)
#12 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(441): WP_CLI\Dispatcher\Subcommand->invoke(Array, Array, Array)
#13 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(464): WP_CLI\Runner->run_command(Array, Array)
#14 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1295): WP_CLI\Runner->run_command_and_exit()
#15 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start()
#16 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/bootstrap.php(83): WP_CLI\Bootstrap\LaunchRunner->process(Object(WP_CLI\Bootstrap\BootstrapState))
#17 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php(32): WP_CLI\bootstrap()
#18 phar:///usr/local/bin/wp/php/boot-phar.php(20): include('phar:///usr/loc...')
#19 /usr/local/bin/wp(4): include('phar:///usr/loc...')
#20 {main}
  thrown in /wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/stellarwp/uplink/src/Uplink/Admin/Package_Handler.php on line 33

    The workaround I’ve found is to run plugin updates with Kadence Blocks excluded from the request wp plugin update --all --skip-plugins=kadence-blocks.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support karlalevelup

    (@karlalevelup)

    Hi, Austin!

    We haven’t received a similar error with WP CLI updates. What we received before is a deprecated message and we were able to release a fix for it in 3.2.18.

    Could you confirm what your PHP version is?

    Regards,
    Karla

    Thread Starter Austin Ginder

    (@austinginder)

    It’s happening for a few different WordPress sites. So far it looks like those sites are on PHP 8.1.18. I tried upgrade one of the affected sites to PHP 8.2.15, same error. I have a Lifetime Full Bundle license however this bug seems to be happening only on website using the free Kadence Blocks plugin. The paid customer websites seem fine.

    Hey, something else is at play, I tested on multiple versions of PHP with different groups of plugins and couldn’t recreate, however the error log does at least give us a path to resolve this. We can update some code to prevent this kind of error. We’ll get it in the next update.

    Ben

    Thread Starter Austin Ginder

    (@austinginder)

    That would be great! I’d be happy to test it out and report back.

    Plugin Support karlalevelup

    (@karlalevelup)

    Hi there!

    This topic has been inactive for more than 2 months. I’ll proceed to mark this as resolved.

    If you have further questions or need additional assistance, feel free to start a new topic.

    Thank you for your understanding!

    Regards,
    Karla

    @britner This appears to still be an issue, fyi. Same error message.

    KadenceWP\KadencePro\StellarWP\Uplink\Admin\Package_Handler::filter_upgrader_pre_download(): Argument #2 ($package) must be of type string, null given, called in /var/www/c7wp.com/htdocs/wp-content/plugins/kadence-pro/vendor/vendor-prefixed/stellarwp/uplink/src/Uplink/Admin/Provider.php on line 172 occurred in wp-content/plugins/kadence-pro/vendor/vendor-prefixed/stellarwp/uplink/src/Uplink/Admin/Package_Handler.php on line 34

    Triggered on sites managed through ManageWP, which uses the CLI to perform updates.

    This is repeatable on all sites using Kadence Blocks, and has been for some time now. I haven’t deep dived to see if a specific plugin is causing a conflict, saw this thread and thought maybe you already had an idea of the cause from before.

    Hey @michaelbourne Which version of Kadence Blocks are you running on the site? If you have a plugin runing null through the wp updater then you would need to update Kadence Blocks to get the fix that we implemented to not have an error show if null is passed. The line errors for example in your message do not match up with the latest version of the Kadence Blocks plugin.

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.