WordPress 404 page after move (web hosting)

When WordPress moved and appeared Only the home page opens, all other pages are 404 errors The common cause of the situation is Fixed link settings are disabled (.htaccess file has not been updated) or the pseudo-static rules are not in effectThe

You can fix this issue directly through code in several ways:

✅ I. Through code rewriting .htaccess(Apache environment)

Add the following code to the theme's functions.php in (only needs to be executed once, it is recommended to add a judgment to avoid multiple executions):

add_action('init', function () {
    $htaccess_path = ABSPATH . '.htaccess';

    // Check if .htaccess exists
    if (!file_exists($htaccess_path) || strpos(file_get_contents($htaccess_path), 'WordPress') === false) {
        $rules = <<<HTACCESS
# BEGIN WordPress

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} ! -f
RewriteCond %{REQUEST_FILENAME} ! -f RewriteCond %{REQUEST_FILENAME} !
RewriteRule . /index.php [L]
</IfModule
# END WordPress
HTACCESS.

        file_put_contents($htaccess_path, $rules);
    }
}).

✅ II. Refresh fixed link structure with code (background setting equivalent operation)

You can also force a refresh of the fixed link rules in the code:

add_action('init', function () {
    if (get_option('permalink_structure') ! == '/%postname%/') {
        update_option('permalink_structure', '/%postname%/');
        flush_rewrite_rules();
    }
}).

📌 Note: You can add conditional judgment to this code, such as running it only once or executing it only when the administrator is logged in.

✅ III. In case of NGINX environments

NGINX is not supported .htaccessYou need to modify the server configuration file /etc/nginx/sites-available/your-site.conf, adding similar rules:

location / {
    try_files $uri $uri/ /index.php?$args;
}

✅ IV. Manual fix program (recommended to perform flush automatically after the background setup is complete)

// Add it to the theme functions.php file
add_action('after_switch_theme', 'flush_rewrite_rules');

🔁 Best Combination Suggestion:

You can combine these two paragraphs if you want to automatically fix the problems after the move:

add_action('init', function () {
    // Set the permalink_structure to /%postname%/.
    if (get_option('permalink_structure') ! == '/%postname%/') {
        update_option('permalink_structure', '/%postname%/');
    }

    // Force the pseudo-static rules to be flushed
    flush_rewrite_rules();

    // Write .htaccess (Apache only)
    $htaccess_path = ABSPATH . '.htaccess';
    if (!file_exists($htaccess_path) || strpos(file_get_contents($htaccess_path), 'WordPress') === false) {
        $rules = <<<HTACCESS
# BEGIN WordPress

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} ! -f
RewriteCond %{REQUEST_FILENAME} ! -f RewriteCond %{REQUEST_FILENAME} !
RewriteRule . /index.php [L]
</IfModule
# END WordPress
HTACCESS.

        file_put_contents($htaccess_path, $rules);
    }
}).

If you are using NGINX + WordPress..htaccess Invalid, just execute flush_rewrite_rules() is sufficient, NGINX rules need to be configured manually or handled by Ops.