Skip to content

Commit 3281048

Browse files
committed
feedback
1 parent 52a28d5 commit 3281048

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

articles/app-service/migrate-wordpress.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.devlang: php
1010
ms.custom: seodec18
1111

1212
---
13-
# Migrate WordPRess on App Service on Linux
13+
# Migrate WordPress on App Service on Linux
1414

1515
This article describes two ways to migrate WordPress from App Service on Windows or external hosting providers to App Service on Linux.
1616

@@ -23,7 +23,7 @@ This article describes two ways to migrate WordPress from App Service on Windows
2323
1. WordPress plugin: All-In-One WP Migration
2424
2. Manual process of migration
2525

26-
## Migrate WordPress with All-In-One WP Migration Plugin
26+
## Migrate WordPress with All-In-One WP Migration plugin
2727

2828
This plugin is popular for migrating sites with ease. This approach is recommended for sites less than 256MB. If it's more, you can either **purchase the premium version** of the plugin or **migrate manually** using the steps outlined in [manual migration process](#manual-migration-process).
2929

@@ -55,11 +55,11 @@ By default, the file upload size for WordPress on Linux App Services is limited
5555
- Then click on the **Dashboard** option shown below it.
5656
- On the dashboard, you will see a button with the label **Empty All Caches**.
5757

58-
## Manual Migration Process
58+
## Manual migration process
5959

6060
The prerequisite is that the WordPress on Linux Azure App Service must have been created with an appropriate hosting plan from here: [WordPress on Linux App Service](https://aka.ms/linux-wordpress).
6161

62-
### Manually Export the data at source site
62+
### Manually export the data at source site
6363

6464
> [!NOTE]
6565
> Depending on the size of your content and your internet connection, this operation could take several minutes.
@@ -69,7 +69,7 @@ The prerequisite is that the WordPress on Linux Azure App Service must have been
6969

7070
1. Export the contents of the source database into an SQL file. You can perform this task either using MySQL client tools like HeidiSQL, [MySQL workbench](https://dev.mysql.com/downloads/workbench/), [PhpMyAdmin](https://docs.phpmyadmin.net/en/latest/setup.html) or through command line interface. For more information on exporting the database, refer to the following [documentation](https://dev.mysql.com/doc/workbench/en/wb-admin-export-import-management.html).
7171

72-
### Manually Import the data at destination site
72+
### Manually import the data at destination site
7373

7474
1. Create a new Wordpress app using our [WordPress on Linux App Service template](https://aka.ms/linux-wordpress)
7575

@@ -104,9 +104,9 @@ The prerequisite is that the WordPress on Linux Azure App Service must have been
104104

105105
![Database Application Settings](./media/app-service-migrate-wordpress/wordpress_database_application_settings.png)
106106

107-
## Post Migration Actions
107+
## Post migration actions
108108

109-
### Install Recommended Plugins
109+
### Install recommended plugins
110110

111111
It's an optional step, after the site migration it is recommended to validate that you have the default recommended/equivalent plugins activated and configured accurate as before. If you're prohibited from not configuring them as per your organization governing policies, then you can uninstall the plugins.
112112

@@ -118,7 +118,7 @@ It's an optional step, after the site migration it is recommended to validate th
118118

119119
- WP Smush plugin is activated and configured properly for image optimization. See [Image Compression](https://github.com/Azure/wordpress-linux-appservice/blob/main/WordPress/wordpress_image_compression.md) for more information on configuration.
120120

121-
### Recommended WordPress Settings
121+
### Recommended WordPress settings
122122

123123
The following WordPress settings are recommended. However, when the users migrate their custom sites, is it up to them to decide whether to use these settings or not.
124124

@@ -127,19 +127,19 @@ The following WordPress settings are recommended. However, when the users migrat
127127
3. Under the comment settings, enable the option to break comments into pages.
128128
4. Show excerpts instead of the full post in the feed.
129129

130-
## Search And Replace (paths and domains)
130+
## Search and replace (paths and domains)
131131

132132
One common issue that users face during migration is that some of the contents of their old site use absolute urls/paths instead of relative ones. To resolve this issue, you can use plugins like [Search and Replace](https://wordpress.org/plugins/search-replace/) to update the database records.
133133

134-
## Configuring Custom Domain
134+
## Configuring custom domain
135135

136136
To configure your site with a custom domain follow the steps described here: Tutorial: [Map existing custom DNS name](app-service-web-tutorial-custom-domain.md?tabs=a%2Cazurecli)
137137

138-
## Migrating Custom Domain
138+
## Migrating custom domain
139139

140140
When you migrate a live site and its DNS domain name to App Service, that DNS name is already serving live traffic. You can avoid DNS resolution downtime by binding the active DNS name to your app as described in [Migrate an active DNS name](manage-custom-dns-migrate-domain.md).
141141

142-
## Updating SSL Certificates
142+
## Updating SSL certificates
143143

144144
If your site is configured with SSL certs, then follow [Add and manage TLS/SSL certificates](configure-ssl-certificate.md?tabs=apex%2Cportal) to configure SSL.
145145

0 commit comments

Comments
 (0)