• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:
    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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

V
Issue WP Toolkit Wordpress Login fails with AIOS Firewall
Replies
1
Views
3K
Peter Debik
P
S
Issue Specified column is not in the row
Replies
1
Views
853
Peter Debik
P
W
Issue scheduled task ERROR | /opt/psa/admin/bin/php -dauto_prepend_file=sdk.php '/opt/psa/admin/plib/modules/wp-toolkit/scripts/instances-auto-update.php'
Replies
3
Views
2K
Wolfgang Reidlinger
W
L
Issue Server backup fails after moving domain to subscription
Replies
6
Views
673
Kaspar@Plesk
Kaspar@Plesk
S
Issue Cannot run media regenerate
Replies
5
Views
1K
southernsons
S
Back
Top