WP-CLI fatal error
-
I’m getting the following when using WP-CLI:
Fatal error: Uncaught TypeError: call_user_func(): Argument #1 ($callback) must be a valid callback, array callback must have exactly two members in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php:1631I eventually traced this to
[...]/event-tickets/src/Tickets/Commerce/Order_Modifiers/API/Coupons.php, in which there are three occasions where WP’s register_rest_route() is called with invalid parameters, this being the offending parameter:'schema' => $this->get_schema()I’m not sure quite what is being intended there, but as you’ll see it gets past the
_doing_it_wrong()checks inregister_rest_route()and causes the fatal error. I’ve commented out those three lines in my local copy, but I’d appreciate it if you could look into this and fix it before the next version, since it does cause WP-CLI to fail — which could be important for some people!
-
Adding our case and output to this thread:
Command:wp plugin listOutput:
Fatal error: Uncaught TypeError: call_user_func(): Argument #1 ($callback) must be a valid callback, array must have exactly two members in <site dir>/wp-includes/rest-api/class-wp-rest-server.php:1631
Stack trace:
#0 <site dir>/wp-includes/rest-api/class-wp-rest-server.php(1572): WP_REST_Server->get_data_for_route('/tribe/tickets/...', Array, 'help')
#1 <site dir>/wp-includes/rest-api/class-wp-rest-server.php(1379): WP_REST_Server->get_data_for_routes(Array, 'help')
#2 <site dir>/wp-includes/rest-api/class-wp-rest-server.php(1292): WP_REST_Server->get_index(Object(WP_REST_Request))
#3 <site dir>/wp-includes/rest-api/class-wp-rest-server.php(1125): WP_REST_Server->respond_to_request(Object(WP_REST_Request), '/', Array, NULL)
#4 <site dir>/wp-content/plugins/woocommerce/includes/cli/class-wc-cli-runner.php(63): WP_REST_Server->dispatch(Object(WP_REST_Request))
#5 phar:///usr/local/bin/wp-cli.phar/vendor/wp-cli/wp-cli/php/class-wp-cli.php(336): WC_CLI_Runner::after_wp_load()
#6 phar:///usr/local/bin/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1375): WP_CLI::do_hook('after_wp_load')
#7 phar:///usr/local/bin/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1267): WP_CLI\Runner->load_wordpress()
#8 phar:///usr/local/bin/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start()
#9 phar:///usr/local/bin/wp-cli.phar/vendor/wp-cli/wp-cli/php/bootstrap.php(83): WP_CLI\Bootstrap\LaunchRunner->process(Object(WP_CLI\Bootstrap\BootstrapState))
#10 phar:///usr/local/bin/wp-cli.phar/vendor/wp-cli/wp-cli/php/wp-cli.php(32): WP_CLI\bootstrap()
#11 phar:///usr/local/bin/wp-cli.phar/php/boot-phar.php(20): include('phar:///usr/loc...')
#12 /usr/local/bin/wp-cli.phar(4): include('phar:///usr/loc...')
#13 {main}
thrown in <site dir>/wp-includes/rest-api/class-wp-rest-server.php on line 1631
Error: There has been a critical error on this website.Learn more about troubleshooting WordPress. There has been a critical error on this website.Thanks for the prompt response!
I don’t object to a new thread, but it does seem like this is an identical issue to @solarianRegarding your followup, we do use Twenty Twenty-One, and I discovered that the error above only occurs when BOTH Event Tickets Version 5.24.2 and WooCommerce Version 9.9.4 are active together; if either is deactivated the error does not occur and the
wpcommand succeeds. (this is with other plugins enabled as well, not just these two)Will continue testing to uncover any further conflicts
The topic ‘WP-CLI fatal error’ is closed to new replies.
