Uncaught Error: Unknown named parameter $bulk
-
I am running WP 6.7.1 PHP 8.3 and SP 6.1.1 and I am still getting the build cron error. The previous solution to remove the jobs via WP Crontrol do not work. The only solution is to disable the background processing.
Fatal error: Uncaught Error: Unknown named parameter $bulk in /var/www/example .com/htdocs/wp-includes/class-wp-hook.php:324
Stack trace: 0 /var/www/example .com/htdocs/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 1 /var/www/example .com/htdocs/wp-includes/plugin.php(565): WP_Hook->do_action() 2 /home/example/home/example/.wp-cli/packages/vendor/wp-cli/cron-command/src/Cron_Event_Command.php(358): do_action_ref_array() 3 /home/example/home/example/.wp-cli/packages/vendor/wp-cli/cron-command/src/Cron_Event_Command.php(238): Cron_Event_Command::run_event() 4 [internal function]: Cron_Event_Command->run() 5 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(100): call_user_func() 6 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher{closure}() 7 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(497): call_user_func() 8 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(441): WP_CLI\Dispatcher\Subcommand->invoke() 9 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(464): WP_CLI\Runner->run_command() 10 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1296): WP_CLI\Runner->run_command_and_exit() 11 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start() 12 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/bootstrap.php(83): WP_CLI\Bootstrap\LaunchRunner->process() 13 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php(32): WP_CLI\bootstrap() 14 phar:///usr/local/bin/wp/php/boot-phar.php(20): include(‘…’) 15 /usr/local/bin/wp(4): include(‘…’) 16 {main}thrown in /var/www/example .com/htdocs/wp-includes/class-wp-hook.php on line 324
- You must be logged in to reply to this topic.