Free software
I will explain a solution for the popular Open-Source tool Filezilla. Other FTP tools might handle charset encoding differently.
FileZilla offers three different charset settings:
- Autodetect
- Force UTF-8
- Use custom charset
Per default, FileZilla tries to detect the correct charset on its own. If this doesn’t work and your server uses some custom charset encoding, you need to set it via the Site Manager. In the tab “Charset”, a custom charset encoding can be specified for each individual server. Once it’s set, the specified charset encoding will be used for all future connections to this server and the filenames will be correct.
First, the Site Address and the WordPress address need to be updated. Go to Settings->General in the WordPress administration area and change the value of these two settings to the new URL. New contents are now created with HTTPS.
Unfortunately, changing the site address does not update URLs in existing contents, so a SQL-Statement to replace the old URLs with new one is required (replace example.org with the URL of the site to move):
UPDATE wp_posts SET post_content = REPLACE(post_content, 'http://www.example.org', 'https:// www.example.org)
Taggings:
Pages
