db.dmp to database.sql problem

  • Resolved brianmurphy

    (@brianmurphy)


    10 years, 7 months ago

    I’ve experienced this with WP 3.8.3 and 3.9.2. I have the latest 0.5.6 Duplicator plugin. The client’s webhosting company is using plesk.

    They have many wordpress installations done in subdirectories:

    /httpdocs/(main wp)
    /httpdocs/subdir1/(wp)
    /httpdocs/subdir2/(wp)
    etc.

    I used duplicator to move one of the subdir sites to a new account and was getting the wordpress You must update your database page and a site with broken theme options.

    After some debugging, it appears the database.sql in archive.zip is an 8 month old DB dump from a different WP installation. But the db.dmp file is a correct current database export. I suspect there is a problem when duplicator resaves db.dmp as database.sql. The timestamped xxxxx_database.sql file in wp_snapshots is the correct current version of the database.

    As a workaround, I manually extracted archive.zip in the new account and rewrote database.sql with the wp-snapshots version. Then when running install.php, I got the site to work.

    If I have time, I will try looking through the plugin source code.

    Thank you for your attention,
    Brian

    https://www.ads-software.com/plugins/duplicator/

Viewing 5 replies - 1 through 5 (of 5 total)

  • Hey Brian,

    That is quite odd, don’t think I have had anyone report that exact issue… If you find something out of sync definitely let me know. The code is also on github.

    Cheers~

    Hi,

    I have some similar problem here. (Using WP 4.0.1 and Duplicator 0.5.8)

    By creating an archive locally, the database.sql in the *_archive.zip is an old version. It has the same state when the database was being installed. The separately created database.sql (not included to the zip) does show the current state with all changes.

    I have to say, that the installation process on this local machine was done with files from another local database (same settings and the site is not live yet) by extracting the *_archive.zip to ..\xampp\htdocs\wordpress without database.sql. The database.sql was imported via phpmyadmin directly. (And not via installer.php)

    How can I fix this issue so that the actual database.sql will be copied into the *_archive.zip?

    Hey Phenar,

    Currently the only way to have the most recent copy of the database.sql file added to the archive.zip file is to create a new package and then download it.

    Cheers~

    Hi Cory,

    Meanwhile:
    – I copied the separately created database.sql into the archive.zip,
    – uploaded and installed on the host server,
    – deleted the local database completely,
    – downloaded the backup from host,
    – and installed locally again.

    No synch problems anymore as before. Thanks, anyway. ??

    Sounds Good! Thxs for the update.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘db.dmp to database.sql problem’ is closed to new replies.