Laravel 5.5集成WordPress后，实现Laravel登录自动同步WordPress后台登录

Alright, let's work through how to automatically log a user into your WordPress backend once they've logged into your Laravel app. You’re already pointed in the right direction with wp_set_auth_cookie()—let’s build out the full, reliable implementation with all the key details you need.

Step 1: Safely Load WordPress Core #

First, you need to pull in WordPress’ core functionality so you can use its authentication functions. Since your WordPress lives in public/blog, use Laravel’s helper to get the correct path, and add a check to avoid errors if the file is missing:

$wpLoadPath = public_path('blog/wp-load.php');
if (!file_exists($wpLoadPath)) {
    // Handle this error appropriately—log it, show a message, or abort
    abort(500, 'WordPress core files could not be loaded');
}
require_once $wpLoadPath;

Step 2: Map Laravel User to WordPress User #

Laravel and WordPress have separate user databases, so you need to find the corresponding WordPress user for your logged-in Laravel user. Assuming your corecel sync uses email as the matching field (adjust if you use username or another attribute):

// Get the currently logged-in Laravel user
$laravelUser = auth()->user();
if (!$laravelUser) {
    // No user is logged in—redirect to Laravel login or handle as needed
    return redirect()->route('login');
}

// Find the WordPress user by matching email
$wpUser = get_user_by('email', $laravelUser->email);
if (!$wpUser) {
    // No matching WordPress user exists—either create one via corecel or show an error
    abort(403, 'No corresponding WordPress account found');
}

$wpUserId = $wpUser->ID;

Step 3: Set WordPress Auth Cookie & Complete Login #

Now use WordPress’ native functions to set the authentication cookie and trigger the necessary login actions. Be sure to configure the cookie path to match your WordPress subdirectory (/blog/) so WordPress recognizes it:

// Set the WordPress authentication cookie
wp_set_auth_cookie(
    $wpUserId,
    true, // Set to true if you want "remember me" functionality
    is_ssl(), // Use secure cookies if your site uses HTTPS
    '/blog/' // Critical: Cookie path matches your WordPress subdirectory
);

// Trigger WordPress' login action to finalize the process (updates login timestamp, etc.)
do_action('wp_login', $wpUser->user_login, $wpUser);

Step 4: Where to Place This Code #

The best spot is in Laravel’s login success callback. Open your LoginController (located at app/Http/Controllers/Auth/LoginController.php) and override the authenticated method:

use Illuminate\Http\Request;

protected function authenticated(Request $request, $user)
{
    // Load WordPress core and auto-login
    $wpLoadPath = public_path('blog/wp-load.php');
    if (file_exists($wpLoadPath)) {
        require_once $wpLoadPath;

        $wpUser = get_user_by('email', $user->email);
        if ($wpUser) {
            wp_set_auth_cookie(
                $wpUser->ID,
                true,
                is_ssl(),
                '/blog/'
            );
            do_action('wp_login', $wpUser->user_login, $wpUser);
        }
    }

    // Redirect to your desired page (Laravel home, WordPress dashboard, etc.)
    return redirect()->intended('/');
}

Key Troubleshooting & Notes #

• Cookie Configuration: Double-check your WordPress site settings (Settings > General) to ensure the "Site Address (URL)" is http://dev.local/blog—this ensures WordPress uses the correct cookie domain and path.
• User Sync Reliability: Make sure your corecel package is syncing user data consistently (email, username, password hashes) so the WordPress user exists and is valid when the login triggers.
• Session Conflicts: Laravel and WordPress use separate session cookies (laravel_session vs. wordpress_*), so conflicts are rare. If you run into issues, verify cookie names and expiration times don’t clash.
• Error Handling: Always include checks for file existence and user matching to avoid unexpected crashes.

内容的提问来源于stack exchange，提问作者Ashvin Jaiswal