cPanel WordPress Manager Error - "/usr/local/bin/php"

CDT

• June 03, 2019 19:25

Greeting everyone... /etc/redhat-release:CentOS release 6.10 (Final) /usr/local/cpanel/version:11.80.0.11 /var/cpanel/envtype:virtuozzo CPANEL=release I have a couple of Wordpress sites I installed "manually" (i.e. server side). I am wanting Wordpress Manager to recognize these sites... after running the "Discover Sites" I get the following error. Screenshot attached. "The system found a new WordPress site, "/home/alamojo/public_html/wp-config.php", but could not make it manageable because of the following error: (XID csn2k9) "/usr/local/bin/php" reported error code "255" when it ended: " Wordpress also returns this error in error_log: "[04-Jun-2019 11:46:11 Pacific/Auckland] PHP Fatal error: Uncaught Error: Call to undefined function add_filter() in phar:///usr/local/cpanel/3rdparty/share/cpanel-wp-cli/wp-cli.phar/vendor/wp-cli/config-command/src/Config_Command.php(358) : eval()'d code:91 Stack trace: #0 phar:///usr/local/cpanel/3rdparty/share/cpanel-wp-cli/wp-cli.phar/vendor/wp-cli/config-command/src/Config_Command.php(358): eval() #1 phar:///usr/local/cpanel/3rdparty/share/cpanel-wp-cli/wp-cli.phar/vendor/wp-cli/config-command/src/Config_Command.php(289): Config_Command::get_wp_config_vars() #2 [internal function]: Config_Command->list_(Array, Array) #3 phar:///usr/local/cpanel/3rdparty/share/cpanel-wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(93): call_user_func(Array, Array, Array) #4 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}(Array, Array) #5 phar:///usr/local/cpanel/3rdparty/share/cpanel-wp-cli/wp-cli.phar/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(449): call_user_func(Object(Closure), Array, Array) # in phar:///usr/local/cpanel/3rdparty/share/cpanel-wp-cli/wp-cli.phar/vendor/wp-cli/config-command/src/Config_Command.php(358) : eval()'d code on line 91 "

• 

  cPanelMichael

  • June 04, 2019 19:20

  Hello @CDT, Can you open a

  0
• 

  CDT

  • June 05, 2019 23:49

  Done Your Support Request ID is: 12503001 Thankyou

  0
• 

  CDT

  • June 06, 2019 01:52

  This was resolved :) Very simple fix [QUOTE] This was occurring due to having 'add_filter( 'auto_update_plugin', '__return_false' );' set within the wp-config.php file. I've commented the variable. [ root@xxx.xxx.xxx.xxx /home/axxxxo/public_html]# grep auto_update_plugin wp-config.php #add_filter( 'auto_update_plugin', '__return_false' ); Afterward, I was able to get the WordPress Manager to work successfully.
  Thanks to JC Newton, Technical Analyst III / Migration Specialist, cPanel L.L.C.

  0
• 

  CDT

  • June 06, 2019 02:20

  Also found the following in wp-config.php is a problem too and needs commenting out :) add_filter( 'auto_update_theme', '__return_false' );

  0
• 

  cPanelMichael

  • June 06, 2019 17:23

  Hello @CDT, I'm glad to see the issue was solved. Thanks for sharing the outcome!

  0

Please sign in to leave a comment.