Restore fails

  • Resolved Eric

    (@winmkt)


    5 years, 5 months ago

    I am trying to migrate a live site to a development environment on my Windows computer using the latest version of WampServer. I backed up the site with the current version of WPvivid to my Dropbox account. Then using WPvivid and the barebones WordPress site on my computer, I uploaded this backup to my development site via the WPvivid upload tab. Then from the WPvivid backups tab I clicked the restore link and selected the migrate option to change the site domain to the virtual host I created on my computer. The restore process starts and then ends with an error. Here is the error message (Note that I edited the path in the error message I pasted below for privacy/security reasons):

    [2019-06-14 14:23:40][error]An error has occurred. class: Error;msg: Maximum function nesting level of ‘256’ reached, aborting!;code: 0;line: 808;in_file: [drive]:[localpath]\wp-content\plugins\wpvivid-backuprestore\includes\class-wpvivid-restore-database.php;

    How can I get this to work? Do I need to modify any settings in WampServer?

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author wpvivid

    (@wpvivid)

    Hello @winmkt
    Thank you for the feedback. This error is rare,
    1. enable the xdebug extension
    then increase the value of xdebug.max_nesting_level in your php.ini
    2. or, disable xdebug extension of php
    Then try restore again, and please tell me if it works, thank you again:)

    • This reply was modified 5 years, 5 months ago by wpvivid.
    Thread Starter Eric

    (@winmkt)

    I disabled the xdebug extension. The restore seems to have made more progress but still ended with an error:

    [2019-06-14 15:56:21][error]Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) file:[drive]:[localpath]\wp-content\plugins\wpvivid-backuprestore\includes\class-wpvivid-restore-database.php line:755

    Before that error, there are a few lines that show cleaning up zip files and the last few lines before that show it was restoring the wp_duplicator_packages table. Do I need to disable Duplicator on my live site before making the backup?

    Plugin Author wpvivid

    (@wpvivid)

    Hello, @winmkt
    Our plugin doesn’t need to disable duplicator.
    This error was triggered by php memory exhausted, which means you got a large website or website database. Please try to assign memory to php_memory_limit, 512MB or higher is better.

    Plugin Author wpvivid

    (@wpvivid)

    Hello, @winmkt
    If the error remains, please send us a debug file via debug-sending feature of website info tab of our plugin. Thank you so much:)

    Thread Starter Eric

    (@winmkt)

    OK, I will try increasing the limit and let you know what happens. According to stats from my host for the live site, the database size is 5MB and the WPvivid backup zip file is 130MB.

    Plugin Author wpvivid

    (@wpvivid)

    Hello,
    OK:)

    Thread Starter Eric

    (@winmkt)

    I increased php_memory_limit first to 512MB and after that failed, I set it to 1GB and that failed too:

    [2019-06-14 16:40:10][error]Allowed memory size of 1073741824 bytes exhausted (tried to allocate 20480 bytes) file:[drive]:[localpath]\wp-content\plugins\wpvivid-backuprestore\includes\class-wpvivid-restore-database.php line:755

    Do I need to increase it even more?

    I’ve sent the debug file to you as you requested.

    Eric

    Plugin Author wpvivid

    (@wpvivid)

    Hi,
    Thank you, the debug file has been received and I will analyze it. Once the problem is solved, I will let you know.

    Plugin Support nicholas2019

    (@nicholas2019)

    As the issue is fixed, I am going to mark it as resolved. Feel free to contact us if you have any questions.

    Thread Starter Eric

    (@winmkt)

    Thank you Nicholas for all of your help!! I was really impressed by all of the assistance I received via email (outside of this forum/message thread) from you and the rest of the WPVivid team!

    Eric

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Restore fails’ is closed to new replies.