Importing package hangs at 63%

  • Resolved jjgouveia69

    (@jjgouveia69)


    3 years, 6 months ago

    Hi. I’m using Prime Mover to migrate a multisite site to a single site.
    With Export site created the package, send it to new server with FTP.
    When importing package it hangs always at 63% with one of two messages: “Importing database tables. Starting… ” or “preparing user meta keys”.
    And finish with an error: “Progress reporting fails for blog ID 1. Retry is attempted but still fails. Server Error : Bad Request”.

    I’ve followed this instructions from another topic:
    —–

    Start with a fresh WordPress installation, you can use WordPress Reset plugin to reset your database to a fresh installation
Delete all files in your /wp-content/uploads/ if its not important since this will be entirely replaced with the migrated package files.
Delete all plugins in /wp-content/plugins/ as they will be replaced with the plugin files from the package except Prime Mover plugin.
Switch to default WordPress theme (2020 for example
Now activate Prime Mover plugin only.
Restore the package directly from WordPress admin since it’s faster and safer than using upload, please follow this tutorial.

    —–
    I don’t see any error log file created by the plugin.

    Thank you.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Codexonics

    (@codexonics)

    Hi,
    Thanks for using Prime Mover. I suspect this is caused by a fatal error related to a plugin conflict. Since you are exporting from a multisite to single site. It’s possible you have included plugins in the export package that are multisite-only. These plugins can cause errors when Prime Mover activates them in single site during restoration process (since this is only needed in multisite).

    To verify this, can you please try adding this to your target site wp-config.php? This will enable debugging and will log errors to /wp-content/debug.log.

    // Enable WP_DEBUG mode
define( 'WP_DEBUG', true );

// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );

// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

    After you enabled WordPress debugging. Please repeat the restore again using this procedure

    Wait until the error is reproduced again (stucked at 63%). Once reproduced, cancel the restore by refreshing the page and see what errors are logged into the debug.log file.

    In addition, Prime Mover also generates an restore log which is accessible in wp-content/uploads/prime-mover-export-files/. Please look for the latest log generated with file name *._migration.log. Zip both debug.log and these migration log. Upload it to Gdrive or etc and share us the URL to download it. Please report the error details by contacting us in our official site or you can report bug inside your WordPress admin by going to Prime Mover -> Contact us and select bug report.

    Once we have all the details, we will know what causes it to stucked. If you are certain that errors are caused by a multisite-only plugin. Please try deactivating them first in the source multisite and re-generate a new export package. And then try restore that new package.

    Thanks and please let me know how it goes. ??

    Plugin Author Codexonics

    (@codexonics)

    Hello,
    If there are no meaningful errors being logged – please share with us the WPRIME package. Please upload it to Gdrive or any cloud platform you choose and share with us the link to download by contacting us. We will try to diagnose this package on our end. This is to see if we are able to reproduce the same error as you have. Thanks!

    Thread Starter jjgouveia69

    (@jjgouveia69)

    Hi.
    That was fantastic. Thanks for the fast resolution of the problem.
    I am very grateful for your commitment and concern.
    Thanks again. Best regards.
    Joao Gouveia

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Importing package hangs at 63%’ is closed to new replies.