Translations

Working directory web visible on %1$s. Please fix this and check again.

Working directory web visible on %1$s. Please fix this and check again.

However, if this rule already exists in your working directory, chances are your server is configured to disallow any .htaccess overrides or is unable to parse the .htaccess file (your server doesn't support .htaccess, e.g. NGINX). In this case, you can contact your hosting provider, and ask them to ensure your working directory is not visible and accessible on the web.

However, if this rule already exists in your working directory, chances are your server is configured to disallow any .htaccess overrides or is unable to parse the .htaccess file (your server doesn't support .htaccess, e.g. NGINX). In this case, you can contact your hosting provider, and ask them to ensure your working directory is not visible and accessible on the web.

Shipper automatically tries to protect your working directory ( <code>%s</code> ) by adding a protective .htaccess file to your working directory. We add the following .htaccess rule to protect your working directory:

Shipper automatically tries to protect your working directory ( <code>%s</code> ) by adding a protective .htaccess file to your working directory. We add the following .htaccess rule to protect your working directory:

Working directory on <b>%s</b> is visible and accessible on the web.

Working directory on <b>%s</b> is visible and accessible on the web.

The working directory is where Shipper writes its session and some intermediate files during the migration process. Since these files may contain sensitive data, your working directory should not be visible and accessible on the web.

The working directory is where Shipper writes its session and some intermediate files during the migration process. Since these files may contain sensitive data, your working directory should not be visible and accessible on the web.

Temp directory web visible on %1$s. Please fix this and check again.

Temp directory web visible on %1$s. Please fix this and check again.

However, if this rule already exists in your working directory, chances are your server is configured to disallow any .htaccess overrides or is unable to parse the .htaccess file (your server doesn't support .htaccess, e.g. NGINX). In this case, you can contact your hosting provider, and ask them to ensure your temp directory is not visible and accessible on the web.

However, if this rule already exists in your working directory, chances are your server is configured to disallow any .htaccess overrides or is unable to parse the .htaccess file (your server doesn't support .htaccess, e.g. NGINX). In this case, you can contact your hosting provider, and ask them to ensure your temp directory is not visible and accessible on the web.

Shipper automatically tries to protect your temp directory ( <code>%s</code> ) by adding a protective .htaccess file to your working directory, which is one level above. We add the following .htaccess rule to protect your temp directory:

Shipper automatically tries to protect your temp directory ( <code>%s</code> ) by adding a protective .htaccess file to your working directory, which is one level above. We add the following .htaccess rule to protect your temp directory:

Temp directory on <b>%s</b> is visible and accessible on the web.

Temp directory on <b>%s</b> is visible and accessible on the web.

The temp directory is where Shipper writes some temporary files during the migration process. Since these files may contain sensitive data, your temp directory should not be visible and accessible on the web.

The temp directory is where Shipper writes some temporary files during the migration process. Since these files may contain sensitive data, your temp directory should not be visible and accessible on the web.

Unfortunately, Shipper cannot yet migrate your network to another network if the address types are different. Meanwhile, you can use another plugin which supports this type of migration.

Unfortunately, Shipper cannot yet migrate your network to another network if the address types are different. Meanwhile, you can use another plugin which supports this type of migration.

%1$s but %2$s.

%1$s but %2$s.

Multisite networks support two different URL schemes for subsite addresses, i.e., Subdomain (For example: site1.example.com, site2.example.com) and Subdirectory (For example: example.com/site1, example.com/site2). You can define your preferred address type for your network at the time of installation. Since both of these address types are very hard to switch later, because of the way data is stored in the database, Shipper can only migrate from your network if both the installations have the same address type.

Multisite networks support two different URL schemes for subsite addresses, i.e., Subdomain (For example: site1.example.com, site2.example.com) and Subdirectory (For example: example.com/site1, example.com/site2). You can define your preferred address type for your network at the time of installation. Since both of these address types are very hard to switch later, because of the way data is stored in the database, Shipper can only migrate from your network if both the installations have the same address type.

<b>%s</b> is a subdirectory installation

<b>%s</b> is a subdirectory installation

<b>%s</b> is a subdomain installation

<b>%s</b> is a subdomain installation