如何为不同用户角色设置多条件页面跳转规则

Hey there! Let's walk through how to build these multi-condition redirect rules for your site. I'll use PHP for the examples since it's super common for user-based web systems, but the core logic translates to other languages like Node.js, Python, or even framework-specific middleware (e.g., Laravel, Express) too.

First, let's set up two quick helper functions to handle user state checks—these will make our redirect logic cleaner:

// Check if the user is logged in (adjust based on your auth system: sessions, tokens, etc.)
function is_user_logged_in() {
    return isset($_SESSION['user_id']); // Replace with your actual auth check
}

// Get the current user's role (returns 'subscriber', 'customer', or null)
function get_user_role() {
    return $_SESSION['user_role'] ?? null; // Pull from your user session/database
}

1. Redirect unlogged users from Shop page to Register #

Add this logic before any HTML content is sent to the browser (e.g., in a global header include or middleware):

// Check if we're on the shop page and the user isn't logged in
if ($_SERVER['REQUEST_URI'] === '/shop' && !is_user_logged_in()) {
    header('Location: /register');
    exit; // Always exit after a redirect to stop further code execution
}

2. Redirect logged-in Subscribers/Customers from Register to My Account #

This prevents logged-in users from accessing the registration page unnecessarily:

// Check if we're on the register page and the user is logged in
if ($_SERVER['REQUEST_URI'] === '/register' && is_user_logged_in()) {
    $user_role = get_user_role();
    // Redirect both roles to their respective My Account page
    if ($user_role === 'subscriber' || $user_role === 'customer') {
        // Use a single account page, or separate URLs if you have role-specific pages
        header('Location: /my-account');
        // For role-specific accounts: header("Location: /my-account/$user_role");
        exit;
    }
}

3. Redirect logged-in Subscribers (non-Customers) from restricted pages #

Since your original note was incomplete, I'll cover a common scenario: blocking subscribers from customer-only pages (like checkout, order history). Adjust the page list to match your restricted content:

// List of pages only customers should access
$customer_only_pages = ['/checkout', '/order-history', '/customer-exclusive'];

// Check if we're on a restricted page, user is logged in, but not a customer
if (in_array($_SERVER['REQUEST_URI'], $customer_only_pages) && is_user_logged_in()) {
    $user_role = get_user_role();
    if ($user_role === 'subscriber') {
        // Redirect to subscriber account, a permission notice, or an upgrade page
        header('Location: /my-account?message=customer-only');
        // Or send to an upgrade page: header('Location: /upgrade-to-customer');
        exit;
    }
}

Quick Tips:

• Place code correctly: Always run redirect logic before any HTML output—otherwise the header() function will fail.
• Security first: Never rely on client-side checks (like JavaScript) for role restrictions. All validation must happen server-side.
• Adjust URLs: Swap /shop, /register, etc., with your actual page paths.
• Edge cases: Add fallback logic for invalid roles (e.g., redirect to a generic error page if get_user_role() returns something unexpected).

内容的提问来源于stack exchange，提问作者Kenny Amaro