Migration between environments in Wordpress - Mini Project: Build & Apply

Migration between environments

📖 Scenario: You are managing a WordPress website and need to move it from a local development environment to a live server. This process is called migration. It involves copying the database and files, then updating configuration settings so the site works correctly on the new server.

🎯 Goal: Build a simple migration setup by creating a configuration file with environment details, then write code to switch between local and live settings automatically.

📋 What You'll Learn

Create a PHP array with local and live environment settings

Add a variable to select the current environment

Write code to load the correct settings based on the selected environment

Complete the configuration so WordPress can use the correct database and URL

💡 Why This Matters

🌍 Real World

Web developers often need to move WordPress sites from local machines to live servers. This setup helps manage different settings easily without manual changes.

💼 Career

Knowing how to configure WordPress for multiple environments is essential for developers working on real projects, ensuring smooth deployment and fewer errors.

1

Create environment settings array

Create a PHP array called $environments with two keys: 'local' and 'live'. Each key should have an array with these exact entries: 'DB_NAME' => 'wp_local_db', 'DB_USER' => 'local_user', 'DB_PASSWORD' => 'local_pass', 'DB_HOST' => 'localhost', and 'WP_HOME' => 'http://localhost' for 'local'. For 'live', use 'DB_NAME' => 'wp_live_db', 'DB_USER' => 'live_user', 'DB_PASSWORD' => 'live_pass', 'DB_HOST' => 'livehost', and 'WP_HOME' => 'https://www.example.com'.

Wordpress

<?php
// Create the $environments array with local and live settings
# Your code here

Hint

Use a PHP associative array with keys 'local' and 'live'. Each key holds another associative array with the exact database and URL settings.

2

Set current environment variable

Add a variable called $current_env and set it to the string 'local' to select the local environment.

Wordpress

 [
        'DB_NAME' => 'wp_local_db',
        'DB_USER' => 'local_user',
        'DB_PASSWORD' => 'local_pass',
        'DB_HOST' => 'localhost',
        'WP_HOME' => 'http://localhost'
    ],
    'live' => [
        'DB_NAME' => 'wp_live_db',
        'DB_USER' => 'live_user',
        'DB_PASSWORD' => 'live_pass',
        'DB_HOST' => 'livehost',
        'WP_HOME' => 'https://www.example.com'
    ]
];

// Set the current environment
# Your code here

Hint

Just create a variable named $current_env and assign it the string 'local'.

3

Load settings for current environment

Create a variable called $config and set it to the array inside $environments that matches the key in $current_env. Use $environments[$current_env] to get the correct settings.

Wordpress

 [
        'DB_NAME' => 'wp_local_db',
        'DB_USER' => 'local_user',
        'DB_PASSWORD' => 'local_pass',
        'DB_HOST' => 'localhost',
        'WP_HOME' => 'http://localhost'
    ],
    'live' => [
        'DB_NAME' => 'wp_live_db',
        'DB_USER' => 'live_user',
        'DB_PASSWORD' => 'live_pass',
        'DB_HOST' => 'livehost',
        'WP_HOME' => 'https://www.example.com'
    ]
];

$current_env = 'local';

// Load the config for the current environment
# Your code here

Hint

Use the $current_env variable as a key to get the right array from $environments.

4

Complete WordPress configuration with environment settings

Use the $config array to define the WordPress constants: DB_NAME, DB_USER, DB_PASSWORD, DB_HOST, and WP_HOME. Use define('DB_NAME', $config['DB_NAME']) and similarly for the others.

Wordpress

 [
        'DB_NAME' => 'wp_local_db',
        'DB_USER' => 'local_user',
        'DB_PASSWORD' => 'local_pass',
        'DB_HOST' => 'localhost',
        'WP_HOME' => 'http://localhost'
    ],
    'live' => [
        'DB_NAME' => 'wp_live_db',
        'DB_USER' => 'live_user',
        'DB_PASSWORD' => 'live_pass',
        'DB_HOST' => 'livehost',
        'WP_HOME' => 'https://www.example.com'
    ]
];

$current_env = 'local';

$config = $environments[$current_env];

// Define WordPress constants using $config
# Your code here

Hint

Use the PHP define function to set each constant with the matching value from $config.

Practice

1. What is the main purpose of migrating a WordPress site between environments?

easy

A. To move the site safely from one place to another

B. To change the site's theme permanently

C. To delete all plugins and start fresh

D. To increase the site's loading speed automatically

Solution

1. Step 1: Understand migration meaning

   Migration means moving a site from one environment (like local or staging) to another (like live).

2. Step 2: Identify the main goal

   The goal is to move the site safely without losing data or breaking it.

3. Final Answer:

   To move the site safely from one place to another -> Option A

4. Quick Check:

   Migration = safe site move [OK]

Hint: Migration means moving site safely between places [OK]

Common Mistakes:

• Thinking migration changes themes automatically
• Assuming migration deletes plugins
• Believing migration speeds up site by itself

2. Which of the following is the correct way to update URLs after migrating a WordPress site?

easy

A. Change URLs only in the wp-config.php file

B. Manually edit URLs in the database using a search and replace tool

C. Leave URLs as they are; WordPress updates them automatically

D. Delete the .htaccess file to reset URLs

Solution

1. Step 1: Recognize URL update necessity

   After migration, URLs often need updating to match the new domain or path.

2. Step 2: Choose the correct method

   Using a search and replace tool on the database is the proper way to update all URLs safely.

3. Final Answer:

   Manually edit URLs in the database using a search and replace tool -> Option B

4. Quick Check:

   Update URLs with search and replace [OK]

Hint: Use search and replace tool on database URLs [OK]

Common Mistakes:

• Thinking wp-config.php controls URLs
• Assuming WordPress auto-updates URLs always
• Deleting .htaccess breaks site rules

3. After migrating a WordPress site manually, which step ensures the media files are correctly moved?

medium

A. Change the site URL in wp-config.php

B. Only export the database; media files move automatically

C. Reinstall all plugins to restore media files

D. Copy the wp-content/uploads folder to the new environment

Solution

1. Step 1: Identify media file location

   Media files are stored in the wp-content/uploads folder in WordPress.

2. Step 2: Ensure media files move

   Copying this folder to the new environment keeps all media intact.

3. Final Answer:

   Copy the wp-content/uploads folder to the new environment -> Option D

4. Quick Check:

   Media files = wp-content/uploads copy [OK]

Hint: Copy uploads folder to move media files [OK]

Common Mistakes:

• Thinking media files move with database only
• Reinstalling plugins does not restore media
• Changing wp-config.php does not move files

4. You migrated your WordPress site but see broken links and missing images. What is the most likely cause?

medium

A. You forgot to update URLs in the database after migration

B. You copied the uploads folder twice

C. You changed the site URL in the wp-config.php file correctly

D. You used a plugin to migrate the site

Solution

1. Step 1: Analyze symptoms

   Broken links and missing images usually mean URLs still point to the old site.

2. Step 2: Identify cause

   If URLs in the database are not updated, links break after migration.

3. Final Answer:

   You forgot to update URLs in the database after migration -> Option A

4. Quick Check:

   Broken links = URLs not updated [OK]

Hint: Broken links? Check database URLs first [OK]

Common Mistakes:

• Assuming copying uploads twice fixes links
• Thinking changing wp-config.php fixes broken links
• Believing plugins always fix URL issues automatically

5. You want to migrate a WordPress site from a local environment to a live server. Which sequence of steps is best practice?

hard

A. Install WordPress fresh on live, then copy themes and plugins manually

B. Copy wp-content folder only, then change site URL in wp-config.php

C. Export database, copy wp-content folder, update wp-config.php, replace URLs in database

D. Export database and import it on live, no need to copy files

Solution

1. Step 1: Export database and copy files

   Exporting the database and copying the wp-content folder moves content and media.

2. Step 2: Update configuration and URLs

   Update wp-config.php for database access and replace URLs in the database to match live site.

3. Final Answer:

   Export database, copy wp-content folder, update wp-config.php, replace URLs in database -> Option C

4. Quick Check:

   Full migration = DB export + files + config + URL update [OK]

Hint: Export DB, copy files, update config and URLs [OK]

Common Mistakes:

• Copying files without exporting database
• Changing wp-config.php without URL updates
• Installing fresh WordPress loses content