Broken Wordpress Instance (WP ToolKit)

[Julien]

Hi, I have several Wordpress installations that I've done manually, without using wp toolkit. They are detected with wp toolkit, but reported as broken. Is there a way to make them working with wp toolkit ?
Ubuntu 16.04.04 LTS
Plesk Onyx 17.8.11 update #4
wp toolkit 3.0.4-861

 

[MarkM]

Try renaming the folder it’s installed in, then creating a new toolkit install, delete that folder, then renaming the actual install back... not exactly sure if this would work but that would be my suggestion.

 

[Julien]

Try renaming the folder it’s installed in, then creating a new toolkit install, delete that folder, then renaming the actual install back... not exactly sure if this would work but that would be my suggestion.

Ok, but is there an official way to do this?

 

[Aleksey Filatev]

WordPress Toolkit detect an instance by the following marks:

• Directory "wp-includes" present
• Directory "wp-content" present
• File "wp-config.php" present on the same level or in the parent directory

Then we try to operate with this this instance using WP-CLI utility. If something went wrong, instance will be marked as broken.

Could you please clarify, which PHP version do you use? Which directories structure do you have? Is it customized somehow?

 

[Julien]

Hello Aleksey, standard WP installation, see directory structure attached. No customization. PHP 7.2.4.

 

[Brujo]

usually when instances are shown broken in plesk panel wordpress toolkit during scan there might be an error shown or an entry in the /var/log/plesk/panel.log

 

[Julien]

usually when instances are shown broken in plesk panel wordpress toolkit during scan there might be an error shown or an entry in the /var/log/plesk/panel.log

Failed to parse wp-config.php: Uncaught TypeError: Argument 1 passed to WP_CLI\Runner::WP_CLI\{closure}() must be an instance of Exception, instance of ParseError given in /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1682
Stack trace:
#0 [internal function]: WP_CLI\Runner->WP_CLI\{closure}(Object(ParseError))
#1 {main}
thrown on line 1682
{"err_code":true,"err_message":"Failed to parse wp-config.php: Uncaught TypeError: Argument 1 passed to WP_CLI\\Runner::WP_CLI\\{closure}() must be an instance of Exception, instance of ParseError given in \/opt\/psa\/admin\/plib\/modules\/wp-toolkit\/vendor\/wp-cli\/wp-cli\/php\/WP_CLI\/Runner.php:1682\nStack trace:\n#0 [internal function]: WP_CLI\\Runner->WP_CLI\\{closure}(Object(ParseError))\n#1 {main}\n thrown on line 1682"}

 

[Brujo]

Afaik thats happens when in your wp-config.php are entrys which shouldnt be there...

Take into consider to compare a actual Version of wp-config with yours and see the difference

and see also: WordPress instance is marked as broken: Uncaught TypeError: Argument 1 passed to WP_CLI

 

[Julien]

Afaik thats happens when in your wp-config.php are entrys which shouldnt be there...

Take into consider to compare a actual Version of wp-config with yours and see the difference

and see also: WordPress instance is marked as broken: Uncaught TypeError: Argument 1 passed to WP_CLI

Downloaded latest version of wp-config-sample.php, changed the database / password. Uploaded the new wp-config.php
FIXED !