confusing workflow

  • Resolved alx359

    (@alx359)


    6 years, 4 months ago

    I’m probably dense, but can’t help but feel confused of how restore should work.

    – The export & backup tabs create a zip file stored in wp-content\webtoffee_migrations\2018-11-01-03-35-57pm.zip. Mine is about 1.5GB.
    – But I also see a database.sql remaining in wp-content\uploads. (Noticed the same database.sql is already in the zip.)
    – The Import tab is deludingly simple though. It indeed has just one button: Import Migration Package but it just opens the media manager, with all its built-in limitations. I can’t see the zip file I just made, though.

    My questions:
    – How do I actually restore a site from a zip, especially if it’s over 1.5GB?
    – Why the remaining database.sql in wp-content\uploads? Has it any use or is just a redundancy?
    – Why the need of the media uploader at all?! Why not simply a ‘restore’ button in the ‘backup’ section, for each zip already found in the wp-content\webtoffee_migrations\ folder (like “AIO WP Migration” does it)?

    Otherwise, the plugin seems exactly what I’d need. Making localhost backups and migrations to a stage site online. (Especially if you’d consider supporting backup/restore of just the sql file.)

    Thanks for the clarifications.

Viewing 1 replies (of 1 total)
  • Plugin Author WebToffee

    (@webtoffee)

    Hi @alx359

    A) How do I actually restore a site from a zip, especially if it’s over 1.5GB?

    Below steps will help to tackle the upload limit of WP

    1. Copy some random zip file (below 2Mb) to media library with the same name exported from WordPress Migration & Duplicator (eg: 2018-09-06-05-51-02AM.ZIP )

    2. Once it gets uploaded, replace the uploaded file with the original file via FTP (wp-content/uploads/YEAR/MONTH ) with ( exported from WordPress Migration & Duplicator )

    3. Go to the Import tab from the plugin and select the specific file to import

    Note: Even though the solution is for upload_max_filesize, sometimes it may also depend on max_execution_time set on the server.

    B) Why the remaining database.sql in wp-content\uploads? Has it any use or is just a redundancy?

    The database.sql file is added to the concerned zip from the uploads location.
    It has no use after that, will be removing it after compression in coming version.

    C) Why the need of the media uploader at all?! Why not simply a ‘restore’ button in the ‘backup’ section, for each zip already found in the wp-content\webtoffee_migrations\folder (like “AIO WP Migration” does it)?

    Thanks for your suggestion, we will be adding this option in coming versions.

Viewing 1 replies (of 1 total)
  • The topic ‘confusing workflow’ is closed to new replies.