• Resolved werewolph

    (@werewolph)


    Hi. Trying to restore subsite as a single and getting error while restoring on clean WP instalation: [error] => Unable to find the correct SQL path. What i need to do?

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

    (@codexonics)

    Hello,
    Thanks for using Prime Mover as your migration / backup solution. Yes, this is a confirmed bug with the current version.
    Can you please try these steps to fix this?

    1. Download this hotfix: https://codexonics.com/prime-mover/hotfix/prime-mover-free.1.1.0.zip
    2. Delete your old Prime Mover plugin copy and replace it with this new hotfix version.
    3. Re-generate export so the SQL file is there inside the zip package.
    4. Restore and see if you still see this error.

    Please confirm if the hotfix fixes the issue then I’ll release a new version for this bug. Thanks for reporting !

    Thread Starter werewolph

    (@werewolph)

    Thanks, but same error: https://prntscr.com/shzzzl

    Plugin Author Codexonics

    (@codexonics)

    Thanks, did the export zip package includes .sql file on it? Can you please send the entire log report output on the Codexonics contact page? I’ll check and see what’s wrong on it.

    Thread Starter werewolph

    (@werewolph)

    No, there is no sql file inside. – https://prntscr.com/si07m4 Report is sended.

    Plugin Author Codexonics

    (@codexonics)

    Thanks for import log. The export zip package does not have .sql file on it, that’s the reason of the error on the import/restoration end.

    You will need to re-generate the export using the hotfix version here: https://codexonics.com/prime-mover/hotfix/prime-mover-free.1.1.0.zip

    Use that version to create your export at your source site.

    You can test this quickly by just exporting database only to check if it works and make sure the output zip now includes .SQL file on it.

    Does generating export using the hotfix version now includes SQL file on it?
    If there is no SQL, please send the export log to me and I will check.

    This issue is on the export side not on the import side. Let me know the test results.

    Plugin Author Codexonics

    (@codexonics)

    You will need to delete your current Prime Mover version at export/source site and replace that with this version here: https://codexonics.com/prime-mover/hotfix/prime-mover-free.1.1.0.zip

    Simply delete the current version and replace that with the hotfix version . Then test by exporting database only (so it will finish quickly just for testing purposes).

    Thread Starter werewolph

    (@werewolph)

    Stil no sql file inside archieve. How can i get export logs?

    Plugin Author Codexonics

    (@codexonics)

    That’s weird, by the way you can find the export log in /wp-content/uploads/prime-mover-export-files/. Find the file with name like xxxx_xxxx_migration.log. Just get the latest log. Thanks for the test.

    Thread Starter werewolph

    (@werewolph)

    sent you through contact form

    Plugin Author Codexonics

    (@codexonics)

    Thank you, please give me time to analyze the logs. Also can you please send me your site server PHP info? You can share your phpinfo output via pastebin.

    Plugin Author Codexonics

    (@codexonics)

    OK I’ve analyzed the log and it seems there is some incompatibility with your server with the plugin shell dump method. Can you please try adding this to your wp-config.php at export / source site? And then test again?


    define('PRIME_MOVER_SLOW_WEB_HOST', true);

    This will use native PHP dump method. This should hopefully fixed the issue – your package should now include SQL file. Let me know how it goes.

    Thread Starter werewolph

    (@werewolph)

    Works with

    define('PRIME_MOVER_SLOW_WEB_HOST', true);

    in WP-config. Thanks!

    Plugin Author Codexonics

    (@codexonics)

    Great thanks for the update, glad to know it works ??

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Unable to find the correct SQL path’ is closed to new replies.