The system validation checks help to make sure the system is ready for install.
Permissions
Deployment Path: |
|
Suhosin Extension: |
Enabled" : "Disabled"; ?> |
PHP Safe Mode: |
Enabled" : "Disabled"; ?> |
The deployment path must be writable by PHP in order to extract the archive file. Incorrect permissions and extension such as
suhosin can sometimes interfere with PHP being able to write/extract files.
Please see the
FAQ permission help link for complete details.
PHP with
safe mode should be disabled. If Safe Mode is enabled then
please contact your hosting provider or server administrator to disable PHP safe mode.
PHP Mysqli
Support for the PHP
mysqli extension is required.
Please contact your hosting provider or server administrator to enable the mysqli extension.
The detection for this call uses
the function_exists('mysqli_connect') call.
PHP Version
This server is running:
PHP .
A minimum of PHP 5.3.8+ is required. PHP 7.0+ is recommended.
If this requirement fails contact your host or server administrator and let them know you would like to upgrade your PHP version.
For more information on this topic see the FAQ titled
What version of PHP Does Duplicator Support?
Managed Environment
The installer has detected that this server is possibly in a managed hosting setup. The followings checks
have been made which will not allow the installer to continue.
Current host is not managed.
-
Managed system: It appears the installer is being executed on "' . $mh_manager->getHosting($managed_host)->getLabel() . '". Managed hosting is not presently supported in Duplicator Lite.'
: "No restrictions have been found for this host." ?>
-
Configuration file: wpConfigIsNotWriteable()
? "The WordPress configuration file (wp-config.php) must be accessible and writeable to the installer"
: "The wp-config.php is accessible to the installer." ?>
-
Core Directories: notAccessibleCoreDirPresent() > 0
? "The WordPress core directories wp-admin, wp-content and wp-includes must be accessible and writeable to the installer"
: "The WordPress core directories are accessible to the installer"; ?>
Warn
Overwrite Install (Beta)
installSiteOverwriteOn || $is_dbonly) { ?>
WARNING: The Duplicator installer file is currently placed in a location that has an existing WordPress site!
Continuing with this install process will overwrite all existing files and the database associated with this WordPress site. Only continue
with this process if this site is no longer needed.
Deployment Path:
installSiteOverwriteOn || $is_dbonly) { ?>
Duplicator is in "Overwrite Install (Beta)" mode because it has detected an existing WordPress site at the deployment path above. This mode allows for the installer
to be dropped directly into an existing WordPress site and overwrite its contents. Any content inside of the archive file
will overwrite the existing contents in the deployment path above. To continue choose one of these options:
- Ignore this notice and continue with the install to overwrite this WordPress site.
- Move the installer and archive to an empty directory. Then install from there to keep this site intact.
Notice: Existing content such as plugin/themes/images will still show-up after the install is complete if they did not already exist in
the archive file. For example, if plugin X is in the current site but that same plugin X does not exist in the archive file
then that plugin will display as a disabled plugin after the install is completed. The same concept with themes, images and files apply.
This will not impact the site's operation, and the behavior is expected since the install process only extracts the archive files to the deployment
path.
Recommendation: It is recommended you only overwrite WordPress sites that have no value, such as a temporary staging site. On step 2
of this installer you will be given the option to change the database if needed. However, by default the current sites database will be
replaced with the one in this Duplicator package.
Duplicator works best by placing the installer and archive files into an empty directory. If a wp-config.php file is found in the extraction
directory it might indicate that a pre-existing WordPress site exists which can lead to a bad install.
Options:
- If the archive was already manually extracted then [Enable Manual Archive Extraction]
- Empty the directory of all files, except for the installer.php and archive.zip/daf files.
- Advanced Users: Can attempt to manually remove the wp-config file only if the archive was manually extracted.
Warn
Archive Extracted
Deployment Path:
The installer has detected that the archive file has been extracted to the deployment path above. To continue choose one of these options:
- Skip the extraction process by [enabling manual archive extraction]
- Ignore this message and continue with the install process to re-extract the archive file.
Note: This test looks for a file named dup-wp-config-arc__[HASH].txt in the dup-installer directory. If the file exists then this notice is shown.
The dup-wp-config-arc__[HASH].txt file is created with every archive and removed once the install is complete. For more details on this process see the
manual extraction FAQ.
Warn
Database Only
Deployment Path:
The installer has detected that a WordPress site does not exist at the deployment path above. This installer is currently in 'Database Only' mode because that is
how the archive was created. If core WordPress site files do not exist at the path above then they will need to be placed there in order for a WordPress site
to properly work. To continue choose one of these options:
- Place this installer and archive at a path where core WordPress files already exist to hide this message.
- Create a new package that includes both the database and the core WordPress files.
- Ignore this message and install only the database (for advanced users only).
Note: This test simply looks for the directories and a wp-config.php file. If they are not found in the
deployment path above then this notice is shown.
Package Age
This package is day(s) old. Packages older than 180 days might be considered stale. It is recommended to build a new
package unless your aware of the content and its data. This is message is simply a recommendation.
PHP Version Mismatch
You are migrating site from the PHP {$packagePHP} to the PHP {$currentPHP}.
"
."If this servers PHP version is different from the PHP version of where the package was created it might cause problems with various parts of your website
and/or plugins and themes. It is highly recommended to try and use the same version of PHP if you are able to do so. This is simply a warning
and in the event no problems arise then you can igonre this message.
";
?>
PHP Open Base
Open BaseDir: Disabled" : "
Enabled"; ?>
If
open_basedir is enabled and your
having issues getting your site to install properly; please work with your host and follow these steps to prevent issues:
- Disable the open_basedir setting in the php.ini file
- If the host will not disable, then add the path below to the open_basedir setting in the php.ini
""
- Save the settings and restart the web server
Note: This warning will still show if you choose option #2 and open_basedir is enabled, but should allow the installer to run properly. Please work with your
hosting provider or server administrator to set this up correctly.
PHP Timeout
Archive Size: (detection limit is set at )
PHP max_execution_time: (zero means not limit)
PHP set_time_limit: Success' : '
Failed' ?>
The PHP
max_execution_time setting is used to
determine how long a PHP process is allowed to run. If the setting is too small and the archive file size is too large then PHP may not have enough
time to finish running before the process is killed causing a timeout.
Duplicator attempts to turn off the timeout by using the
set_time_limit setting. If this notice shows as a warning then it is
still safe to continue with the install. However, if a timeout occurs then you will need to consider working with the max_execution_time setting or extracting the
archive file using the 'Manual Archive Extraction' method.
Please see the
FAQ timeout help link for more details.
WordPress Multisite
Status:
Duplicator does not support WordPress Multisite (MU) migrations. We recommend using Duplicator Pro which currently supports full Multisite migrations and
subsite to standalone site migrations.
While it is not recommended you can still continue with the build of this package. Please note that after the install the site may not be working correctly.
Additional manual custom configurations will need to be made to finalize this Multisite migration.
[upgrade to pro]
WordPress wp-config Location
If the wp-config.php file was moved up one level and out of the WordPress root folder in the package creation site then this test will show a warning.
This Duplicator installer will place this wp-config.php file in the WordPress setup root folder of this installation site to help stabilize the install process.
This process will not break anything in your installation site, but the details are here for your information.
WordPress wp-content Location
If the wp-content directory was moved and not located at the WordPress root folder in the package creation site then this test will show a warning.
Duplicator Installer will place this wp-content directory in the WordPress setup root folder of this installation site. It will not break anything in your installation
site. It is just for your information.
Sufficient Disk Space
Wordfence
Wordfence Firewall: detected at {$parentWordFencePath}" : "
not detected"; ?>
The Wordfence Web Application Firewall is a PHP based, application level firewall that filters out malicious
requests to your site. Sometimes Wordfence returns false positives on requests done during the installation process,
because of which it might fail. We recommend turning off the Wordfence firewall of the WordPress instance located at the mentioned path.