Overview
Overwrite mode is available in both Pro and Lite versions. The Overwrite Install process lets users replace (overwrite) an existing WordPress sitewith the contents of the archive.zip/daf file. The process for overwrite mode is very close to the Classic Install process, with the main differences being:
- Classic Install requires an empty directory with only the installer.php and archive.zip/daf files.
- Overwrite install will replace any existing files and the Database of the current WordPress site.
- Overwrite install automatically detects the existing site’s database and pre-fills the database credentials.
Duplicator Lite
- Create Package: Duplicator > Packages > “Create New” > Package Files [installer.php & archive.zip] on source site
- Transfer Package: Copy (FTP/cPanel/ect) package files to root of existing WordPress destination site
- Run Installer: In web browser open installer.php file on destination site (site to overwrite)
- Step 1: The “Mode” in the upper right corner should show “Overwrite Install” check the overwrite notice checkbox and continue
- Step 2: The Database inputs will be pre-filled from the existing wp-config.php settings. Check these values and continue
- Step 3/4: Continue through these steps and login to your newly overwritten WordPress site.
Duplicator Pro
- Create Package: Duplicator Pro > Packages > “Create New”
- Transfer Package: Copy (FTP/cPanel/ect) Package (installer.php & archive.zip) to root of existing WordPress site
- Run Installer: In web browser open installer.php file of transferred package file
- Step 1: The “Mode” in the upper right corner should show “Overwrite Install” check the overwrite notice checkbox and continue
- Step 2: Login to your newly overwritten WordPress site.
Notes
Overwrite notice for Pro and Lite: Existing content such as plugin/themes/images will still show-up after the installis complete if they did not already exist in the archive file, when using overwrite install mode. For example, if plugin X is in the current site but that same pluginX does not exist in the archive file then that plugin including all its files will still persist.
The plugin will also display as a disabled plugin after the install is completed. The same concept with themes, images and files apply. This will not impact thesite’s operation. The behavior is expected since the install process only extracts the archive files to the deployment path.To guarantee thatonly the archive files are present we recommend a “Classic Install”.