WPMU DEV In Your Language

Translation of Shipper: Bengali

1 2
Prio Original string Translation
Choose the archive engine you want to use for creating the package.zip. We recommend using the <b>Shell Zip</b> method since it uses your server's internal shell commands for creating the zip file. However, if your host doesn't support the Shell Zip method, you can fall back to the <b>ZipArchive</b> method. You have to log in to add a translation. Details

Choose the archive engine you want to use for creating the package.zip. We recommend using the <b>Shell Zip</b> method since it uses your server's internal shell commands for creating the zip file. However, if your host doesn't support the Shell Zip method, you can fall back to the <b>ZipArchive</b> method.

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • tpl/pages/packages/settings/item-archive-body.php:30
Priority of the original:
normal
More links:
or Cancel
Once you've uploaded both the archive and installer files to your new server, you need to visit the installer.php in your browser. To do this, open up your web browser and type in your new website domain along with /installer.php. I.e. <b>https://example.com/installer.php</b>. Follow the instructions on the installer wizard to complete the migration. You have to log in to add a translation. Details

Once you've uploaded both the archive and installer files to your new server, you need to visit the installer.php in your browser. To do this, open up your web browser and type in your new website domain along with /installer.php. I.e. <b>https://example.com/installer.php</b>. Follow the instructions on the installer wizard to complete the migration.

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • tpl/pages/packages/migration/package.php:115
Priority of the original:
normal
More links:
or Cancel
The next step is to upload both the package archive and installer files to the root directory of your destination server. We recommend uploading them via FTP using an FTP client such as <a href="%s" target="_blank">FileZilla</a>. You’ll need an FTP account to connect to your destination server, and if you are not sure how to create an FTP account, please contact your hosting support. You have to log in to add a translation. Details

The next step is to upload both the package archive and installer files to the root directory of your destination server. We recommend uploading them via FTP using an FTP client such as <a href="%s" target="_blank">FileZilla</a>. You’ll need an FTP account to connect to your destination server, and if you are not sure how to create an FTP account, please contact your hosting support.

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • tpl/pages/packages/migration/package.php:94
Priority of the original:
normal
More links:
or Cancel
Andy, we’ve uncovered a few potential issues that may affect the package build and migration process. Take a look through them and action what you like. While you can ignore the warnings, you must fix the errors (if any) to continue your migration. You have to log in to add a translation. Details

Andy, we’ve uncovered a few potential issues that may affect the package build and migration process. Take a look through them and action what you like. While you can ignore the warnings, you must fix the errors (if any) to continue your migration.

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • tpl/modals/packages/preflight/issues.php:11
Priority of the original:
normal
More links:
or Cancel
Files with names longer than 256 characters are listed below. Files with large names can cause issues on some hosts. We recommend excluding them from the migration and uploading them via FTP to your destination. You have to log in to add a translation. Details

Files with names longer than 256 characters are listed below. Files with large names can cause issues on some hosts. We recommend excluding them from the migration and uploading them via FTP to your destination.

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • tpl/modals/packages/preflight/issue-message.php:34
  • tpl/pages/preflight/wizard-files-result-wrapper.php:24
Priority of the original:
normal
More links:
or Cancel
Files over 8MB are listed below. Large files such as media files or backups can cause timeout issues on some budget hosts during the migration. We recommend excluding them from the migration and uploading them via FTP to your destination. You have to log in to add a translation. Details

Files over 8MB are listed below. Large files such as media files or backups can cause timeout issues on some budget hosts during the migration. We recommend excluding them from the migration and uploading them via FTP to your destination.

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • tpl/modals/packages/preflight/issue-message.php:29
  • tpl/pages/preflight/wizard-files-result-wrapper.php:19
Priority of the original:
normal
More links:
or Cancel
1. Most hosts have the ZipArchive extension installed and available by default, but it may not be active. Open your cPanel, and under the Software section, click on select the PHP version option. You'll see your current PHP version, extensions available, and active PHP extensions. Check the zip option, and click on save to activate it. Note that if the zip option is not available in this list, please contact your hosting support, and ask them to install zip extension for you. You have to log in to add a translation. Details

1. Most hosts have the ZipArchive extension installed and available by default, but it may not be active. Open your cPanel, and under the Software section, click on select the PHP version option. You'll see your current PHP version, extensions available, and active PHP extensions. Check the zip option, and click on save to activate it. Note that if the zip option is not available in this list, please contact your hosting support, and ask them to install zip extension for you.

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • tpl/checks/zip-archive.php:38
Priority of the original:
normal
More links:
or Cancel
Shipper uses PHP's built-in ZipArchive class to zip your files on your source website and unzip them on your destination. You need to have this module available on both sites for the migration to run. You have to log in to add a translation. Details

Shipper uses PHP's built-in ZipArchive class to zip your files on your source website and unzip them on your destination. You need to have this module available on both sites for the migration to run.

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • tpl/checks/zip-archive.php:14
Priority of the original:
normal
More links:
or Cancel
If you have SSH access to your hosting account, you can use chmod to change file permissions, which is the preferred method for experienced users only. Run the following command to change the permissions of your working directory: You have to log in to add a translation. Details

If you have SSH access to your hosting account, you can use chmod to change file permissions, which is the preferred method for experienced users only. Run the following command to change the permissions of your working directory:

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • tpl/checks/workdir-writable.php:61
Priority of the original:
normal
More links:
or Cancel
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. You have to log in to add a translation. Details

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.

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • tpl/checks/workdir-accessible.php:46
Priority of the original:
normal
More links:
or Cancel
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. You have to log in to add a translation. Details

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.

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • tpl/checks/tempdir-accessible.php:46
Priority of the original:
normal
More links:
or Cancel
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. You have to log in to add a translation. Details

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.

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • tpl/checks/subdomain-difference.php:20
Priority of the original:
normal
More links:
or Cancel
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. You have to log in to add a translation. Details

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.

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • tpl/checks/storagedir-accessible.php:46
Priority of the original:
normal
More links:
or Cancel
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. You have to log in to add a translation. Details

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.

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • tpl/checks/storagedir-accessible.php:14
Priority of the original:
normal
More links:
or Cancel
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. You have to log in to add a translation. Details

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.

You have to log in to edit this translation.

Meta

Status:
untranslated
References:
  • tpl/checks/servertype-difference.php:15
Priority of the original:
normal
More links:
or Cancel
1 2
Legend:
Current
Waiting
Fuzzy
Old
with warnings

Export as

Translators

Try Free for 7 Days