Translations

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

Storage 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 storage 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 storage directory is not visible and accessible on the web.

Verify that this .htaccess file is present in your working directory, along with the rule above. If not, we recommend you manually add a .htaccess file with the above code, and run Shipper again.

Verify that this .htaccess file is present in your working directory, along with the rule above. If not, we recommend you manually add a .htaccess file with the above code, and run Shipper again.

Shipper automatically tries to protect your storage 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 storage directory:

Shipper automatically tries to protect your storage 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 storage directory:

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

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

Your storage directory is where Shipper stores cache files during the migration. These files contain sensitive information such as migration info, API response cache, tables, and files lists. Even though Shipper obfuscates these files, they can still be penetrated. Therefore, your storage directory should not be visible and accessible on the web.

Your storage directory is where Shipper stores cache files during the migration. These files contain sensitive information such as migration info, API response cache, tables, and files lists. Even though Shipper obfuscates these files, they can still be penetrated. Therefore, your storage directory should not be visible and accessible on the web.

<b>%1$s</b> uses %2$s whereas <b>%3$s</b> uses %4$s.

<b>%1$s</b> uses %2$s whereas <b>%3$s</b> uses %4$s.

Your web server is what handles HTTP requests and returns your site’s content to its visitors. When you are migrating to a different web server, some parts of your site may not work the same on the destination site due to differences in the way web servers handle configurations. Even some plugins work differently on different server types.

Your web server is what handles HTTP requests and returns your site’s content to its visitors. When you are migrating to a different web server, some parts of your site may not work the same on the destination site due to differences in the way web servers handle configurations. Even some plugins work differently on different server types.

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

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

Every server runs on an operating system, and each operating system has a different directory structure and supports different system libraries. When migrating to a server with a different operating system, if your source site has any hard-coded links or some of your plugins depend on system libraries, they may not work as expected in your destination site.

Every server runs on an operating system, and each operating system has a different directory structure and supports different system libraries. When migrating to a server with a different operating system, if your source site has any hard-coded links or some of your plugins depend on system libraries, they may not work as expected in your destination site.

Please, make sure you are using equal versions of the plugin on both migration ends.

Please, make sure you are using equal versions of the plugin on both migration ends.

If that is not what you intended, please initiate an export migration on your source site instead.

If that is not what you intended, please initiate an export migration on your source site instead.

However, we were able to find an existing export that we can use for this migration, so that is what we will use.

However, we were able to find an existing export that we can use for this migration, so that is what we will use.

We experienced issues checking the remote package size.

We experienced issues checking the remote package size.

Your source site is %1$s in size, but we were not able to estimate how long it might take to migrate it fully. Nevertheless, we still recommend that you export your site, rather than importing it, because the export method allows you to exclude large files from the migration, thus speeding up the process.

Your source site is %1$s in size, but we were not able to estimate how long it might take to migrate it fully. Nevertheless, we still recommend that you export your site, rather than importing it, because the export method allows you to exclude large files from the migration, thus speeding up the process.