• Resolved jcurtis-lbc

    (@jcurtis-lbc)


    WP-CLI is the command-line interface for WordPress. Many people use it to maintain their WordPress sites and to perform such things as updating the core, plugins and themes via the command line or with bash scripts. The most recent version of your plugin is preventing simple commands like wp plugin list or wp plugin update --all from running. Here is the error message that outputs on the command line when attempting to run such commands:

    Fatal error: Uncaught Error: Call to a member function check_permission() on null in /home/username/public_html/wp-content/plugins/business-profile/includes/class-settings.php:713 
    Stack trace: 
    #0 /home/username/public_html/wp-content/plugins/business-profile/includes/class-settings.php(692): bpfwpSettings->show_submit_button('premium') 
    #1 /home/username/public_html/wp-includes/class-wp-hook.php(287): bpfwpSettings->load_settings_panel('') 
    #2 /home/username/public_html/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array) 
    #3 /home/username/public_html/wp-includes/plugin.php(478): WP_Hook->do_action(Array) 
    #4 /home/username/public_html/wp-settings.php(546): do_action('init') 
    #5 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1317): require('/home/username...') 
    #6 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1235): WP_CLI\Runner in /home/username/public_html/wp-content/plugins/business-profile/includes/class-settings.php on line 713 
    Error: There has been a critical error on your website.Learn more about debugging in WordPress. There has been a critical error on your website.

    I hope this issue can be addressed so that users (like myself) who rely on WP-CLI to maintain their sites can continue to use your plugin. Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support jaysupport

    (@jaysupport)

    Hi j,

    This is/was similar to the issue you had with 2.0.1 a couple years ago. The way/order in which WP-CLI initializes things seems to be different, so it was just that, when using the CLI, one element from our plugin that needed to be initialized for another element to work wasn’t. We’ve rearranged it to counter this and will release an update shortly with the change.

    Thread Starter jcurtis-lbc

    (@jcurtis-lbc)

    Thank you for your prompt attention on this! Everything seems to be working again now with 2.2.1. I’ll mark this topic as resolved!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Latest version of plugin is breaking WP-CLI’ is closed to new replies.