• Inviting everyone who uses WordPress management tools in Plesk
    The Plesk team is conducting a 60-minute research session that includes an interview and a moderated usability test.
    To participate, please use this link .
    Your experience will help shape product decisions and ensure the tools better support real-world use cases.

Issue Cloning WP throws error

F

fliegerhermi

Regular Pleskian
Hi, when trying to clone a wp-instance into the same abo I get the following error.
Does anyone have an idea on how to solve that?
  • PHP Fatal error: Uncaught TypeError: unserialize(): Argument #1 ($data) must be of type string, array given in /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/search-replace-command/src/WP_CLI/SearchReplacer.php:86
  • Stack trace:
  • #0 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/search-replace-command/src/WP_CLI/SearchReplacer.php(86): unserialize()
  • #1 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/search-replace-command/src/WP_CLI/SearchReplacer.php(88): WP_CLI\SearchReplacer->run_recursively()
  • #2 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/search-replace-command/src/WP_CLI/SearchReplacer.php(57): WP_CLI\SearchReplacer->run_recursively()
  • #3 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/search-replace-command/src/Search_Replace_Command.php(556): WP_CLI\SearchReplacer->run()
  • #4 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/search-replace-command/src/Search_Replace_Command.php(392): Search_Replace_Command->php_handle_col()
  • #5 [internal function]: Search_Replace_Command->__invoke()
  • #6 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(98): call_user_func()
  • #7 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}()
  • #8 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(451): call_user_func()
  • #9 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(371): WP_CLI\Dispatcher\Subcommand->invoke()
  • #10 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(394): WP_CLI\Runner->run_command()
  • #11 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1180): WP_CLI\Runner->run_command_and_exit()
  • #12 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(23): WP_CLI\Runner->start()
  • #13 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/bootstrap.php(74): WP_CLI\Bootstrap\LaunchRunner->process()
  • #14 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/wp-cli.php(27): WP_CLI\bootstrap()
  • #15 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/boot-fs.php(17): require_once('...')
  • #16 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wpt-wp-cli.php(31): require_once('...')
  • #17 {main}
  • thrown in /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/search-replace-command/src/WP_CLI/SearchReplacer.php on line 86
  • Fatal error: Uncaught TypeError: unserialize(): Argument #1 ($data) must be of type string, array given in /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/search-replace-command/src/WP_CLI/SearchReplacer.php:86
  • Stack trace:
  • #0 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/search-replace-command/src/WP_CLI/SearchReplacer.php(86): unserialize()
  • #1 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/search-replace-command/src/WP_CLI/SearchReplacer.php(88): WP_CLI\SearchReplacer->run_recursively()
  • #2 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/search-replace-command/src/WP_CLI/SearchReplacer.php(57): WP_CLI\SearchReplacer->run_recursively()
  • #3 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/search-replace-command/src/Search_Replace_Command.php(556): WP_CLI\SearchReplacer->run()
  • #4 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/search-replace-command/src/Search_Replace_Command.php(392): Search_Replace_Command->php_handle_col()
  • #5 [internal function]: Search_Replace_Command->__invoke()
  • #6 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(98): call_user_func()
  • #7 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}()
  • #8 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(451): call_user_func()
  • #9 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(371): WP_CLI\Dispatcher\Subcommand->invoke()
  • #10 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(394): WP_CLI\Runner->run_command()
  • #11 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1180): WP_CLI\Runner->run_command_and_exit()
  • #12 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(23): WP_CLI\Runner->start()
  • #13 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/bootstrap.php(74): WP_CLI\Bootstrap\LaunchRunner->process()
  • #14 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/wp-cli.php(27): WP_CLI\bootstrap()
  • #15 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/boot-fs.php(17): require_once('...')
  • #16 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wpt-wp-cli.php(31): require_once('...')
  • #17 {main}
  • thrown in /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/search-replace-command/src/WP_CLI/SearchReplacer.php on line 86
  • Error: Es gab einen kritischen Fehler auf deiner Website.Erfahre mehr über die Problembehandlung in WordPress. Es gab einen kritischen Fehler auf deiner Website.

EDIT: I think it was an error due to different php versions.
I created the target manually with php 7.4 instead of 8 and it worked...
 
Last edited:
Thank you for contacting us. This is a know issue EXTWPTOOLK-7374. WP-CLI 2.4 that utilized under the hood of WordPress Toolkit, doesn't fully support PHP8. It will be updated to the latest version in the future release of WordPress Toolkit.
 
BTW, The issue EXTWPTOOLK-7374 was fixed in WPT 5.5.0.
 
You must log in or register to reply here.

Similar threads

S
Issue Plesk Daily Maintenance ReportUsage problem
Replies
0
Views
1K
s.kazimierczak
S
L
Issue Wp Tool Kit Hopelessly Broke
Replies
4
Views
3K
Ladylinux
L
O
Issue plesk not accessible via GUI after restore
Replies
11
Views
4K
opentype
O
J
Resolved .Net Toolkit doesn't work at all anymore after latest upgrade
Replies
1
Views
1K
JAustin
J
R
Issue Error getting administrator credentials: PHP Fatal error: Call to undefined function WC_CLI_Runner::after_wp_load()
Replies
1
Views
3K
Evgeny
E
Back
Top