Translations

4. If none of the above works, you can ask your hosting support to turn off the open_basedir restriction for you.

4. If none of the above works, you can ask your hosting support to turn off the open_basedir restriction for you.

3. You can also edit the Apache configuration file to disable the PHP open_basedir restriction. Open the httpd.conf file. Add the following line of code at the end, and restart your web server.

3. You can also edit the Apache configuration file to disable the PHP open_basedir restriction. Open the httpd.conf file. Add the following line of code at the end, and restart your web server.

2. Open your php.ini file, comment the open_basedir rule, and restart your server. To comment a line of code in the php.ini file, you need to suffixit with a semicolon. So, to comment the open_basedir rule, add a semicolon in the beginning as in: “; open_basedir true”. Commenting is preferred to deleting the rule, in case you want to reactivate it after the migration.

2. Open your php.ini file, comment the open_basedir rule, and restart your server. To comment a line of code in the php.ini file, you need to suffixit with a semicolon. So, to comment the open_basedir rule, add a semicolon in the beginning as in: “; open_basedir true”. Commenting is preferred to deleting the rule, in case you want to reactivate it after the migration.

1. Go to your cPanel > Select PHP Version, and click on Switch to PHP Options link to see the default values of PHP options. Update the value of open_basedir to an empty value, and click on Apply and then Save.

1. Go to your cPanel > Select PHP Version, and click on Switch to PHP Options link to see the default values of PHP options. Update the value of open_basedir to an empty value, and click on Apply and then Save.

We recommend disabling the <b>open_basedir</b> restriction during migrations to ensure things go smoothly.

We recommend disabling the <b>open_basedir</b> restriction during migrations to ensure things go smoothly.

Open_basedir restriction is in effect on <b>%s</b>.

Open_basedir restriction is in effect on <b>%s</b>.

PHP has a security measure called <b>open_basedir</b> which limits which files can be accessed by a PHP script. Usually, it’s set to your root directory or a couple of specific directories. Shipper needs to be able to write in the working directory, storage directory, temp directory, and log directory to work properly. Having open_basedir active is likely to cause migration failures.

PHP has a security measure called <b>open_basedir</b> which limits which files can be accessed by a PHP script. Usually, it’s set to your root directory or a couple of specific directories. Shipper needs to be able to write in the working directory, storage directory, temp directory, and log directory to work properly. Having open_basedir active is likely to cause migration failures.

<b>%1$s</b> is on MySQL v%2$s whereas <b>%3$s</b> is on MySQL v%4$s.

<b>%1$s</b> is on MySQL v%2$s whereas <b>%3$s</b> is on MySQL v%4$s.

WordPress uses MySQL database to store your data, including posts, pages, users, and plugins data. Migrating from one server to another with a significant difference in the MySQL versions can cause issues in your destination site.

WordPress uses MySQL database to store your data, including posts, pages, users, and plugins data. Migrating from one server to another with a significant difference in the MySQL versions can cause issues in your destination site.

Unfortunately, Shipper cannot yet migrate between sites with different WordPress installation type. We're working on adding features which will allow you to extract a single site from a network and move it to a standalone installation, or migrate a single site into a network as a subsite. Meanwhile, you can use another plugin which supports this type of migration.

Unfortunately, Shipper cannot yet migrate between sites with different WordPress installation type. We're working on adding features which will allow you to extract a single site from a network and move it to a standalone installation, or migrate a single site into a network as a subsite. Meanwhile, you can use another plugin which supports this type of migration.

%1$s but %2$s installation.

%1$s but %2$s installation.

Shipper can only migrate between the same WordPress installation types, i.e. from one single site to another single site or from one multisite network to another multisite network. It is necessary for your source and destination sites to have the same WordPress installation.

Shipper can only migrate between the same WordPress installation types, i.e. from one single site to another single site or from one multisite network to another multisite network. It is necessary for your source and destination sites to have the same WordPress installation.

<b>%s</b> is a multisite

<b>%s</b> is a multisite

<b>%s</b> is a single site

<b>%s</b> is a single site

Log directory is not writable on %1$s. Please fix this and check again.

Log directory is not writable on %1$s. Please fix this and check again.