Articles in this section

Unable to clone WordPress multisite: Error: Couldn't find any tables matching: <prefix>_blogs

Plesk for Linux kb: technical ext: wptk

Symptoms

  • Unable to clone WordPress multisite into root directory of existing domain

  • The following error shows up in Plesk

    Error: Couldn't find any tables matching: <prefix>_blogs

  • The following error can be seen in /var/log/plesk/panel.log

    [2023-06-10 07:45:07.035] 3908:648421949d462 ERR [panel] '/usr/local/psa/admin/bin/filemng' 'cnotremariage' 'exec' '/var/www/vhosts/example.com/httpdocs' 'timeout' '1800' '/opt/plesk/php/7.4/bin/php' '-d' 'safe_mode=off
    ' '-d' 'display_errors=on' '-d' 'opcache.enable_cli=off' '-d' 'open_basedir=' '-d' 'error_reporting=0' '-d' 'max_execution_time=1800' '-c' '/var/www/vhosts/system/example.com/etc/php.ini' '/usr/local/psa/admin/plib/modu
    les/wp-toolkit/vendor/wp-cli/wpt-wp-cli.php' '--path=/var/www/vhosts/example.com/httpdocs' '--no-color' 'search-replace' 'example.com' 'example2.com' 'abcDf_blog' failed with code 1.

    stdout:


    stderr:
    Error: Couldn't find any tables matching: abcDf_blog

Cause

This is due to an identified bug ID EXTWPTOOLK-10588 in WP Toolkit.
During the cloning process of a WordPress multisite, a discrepancy between WP Toolkit configuration file and WP Toolkit database is generated for the target domain.

Resolution

This will be fixed in a future WP Toolkit version

Workaround
  1. Start cloning the website from WordPress > example.com > clone

  2. Wait till cloning fails

  3. Refresh WordPress instance by clicking the refresh button in WordPress > example.com, at the right hand side

    Note: This will fix discrepancy between configuration and database

  4. Repeat step 1

Was this article helpful?

Comments

0 comments

Please sign in to leave a comment.