虚拟路径对应不同内容：多页面轻量网站PHP路径结构优化问询

Hey there! Since you've got solid HTML experience and are just dipping your toes into PHP, let's work out a cleaner, more lightweight way to structure your site—no more redundant folders and duplicate index.php files. Here are a few practical, beginner-friendly approaches tailored to your goal:

1. Single Entry Point with URL Rewriting (Most Recommended) #

This method uses one central index.php file as the gateway for all pages, eliminating nested folders entirely. It’s scalable, clean, and keeps your filesystem lean.

Step 1: Build the Central Router #

Create an index.php in your root folder to handle routing. We’ll use a whitelist to keep things secure (critical to block malicious path-traversal attacks):

<?php
// Define allowed pages to restrict unauthorized access
$allowed_pages = [
    'settings/language',
    'settings/privacy',
    'home' // Add your homepage if needed
];

// Get the requested page from the URL (default to home if none specified)
$requested_page = $_GET['page'] ?? 'home';

// Validate and load content
if (in_array($requested_page, $allowed_pages)) {
    // Map the page path to a single content file (e.g., in a `content` folder)
    $content_file = __DIR__ . '/content/' . str_replace('/', '-', $requested_page) . '.php';
    file_exists($content_file) ? include $content_file : include __DIR__ . '/content/404.php';
} else {
    include __DIR__ . '/content/404.php';
}
?>

Step 2: Store Content in a Single Folder #

Make a content folder in your root, then add files like settings-language.php and settings-privacy.php—these will hold your HTML/PHP content for each page.

Step 3: Clean URLs with Rewriting #

To make URLs look polished (e.g., yoursite.com/settings/language instead of yoursite.com/index.php?page=settings/language), add an .htaccess file (for Apache) to your root:

RewriteEngine On
# Skip existing files/directories to avoid breaking assets
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
# Rewrite all requests to index.php with the page parameter
RewriteRule ^(.*)$ index.php?page=$1 [L]

For Nginx, add this to your server block:

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

2. Consolidate Settings into One File #

If you want to skip extra folders entirely, combine all settings-related pages into a single settings.php file. Use a URL parameter to switch between sections:

<?php
$section = $_GET['section'] ?? '';
?>
<!DOCTYPE html>
<html>
<head>
    <title>Settings</title>
</head>
<body>
    <nav>
        <a href="settings?section=language">Language</a> | 
        <a href="settings?section=privacy">Privacy Policy</a>
    </nav>

    <?php
    switch ($section) {
        case 'language':
            ?>
            <h1>Language Settings</h1>
            <!-- Your language settings HTML/PHP here -->
            <?php
            break;
        case 'privacy':
            ?>
            <h1>Privacy Policy</h1>
            <!-- Your privacy policy HTML/PHP here -->
            <?php
            break;
        default:
            ?>
            <h1>Settings Dashboard</h1>
            <p>Select a section above.</p>
            <?php
            break;
    }
    ?>
</body>
</html>

This cuts down to one settings.php file instead of two folders with duplicate index.phps.

3. Ultra-Minimal: All Content in One File #

For absolute minimalism (great for tiny sites), put all pages directly into the root index.php and use a parameter to toggle content:

<?php
$page = $_GET['page'] ?? 'home';
?>
<!DOCTYPE html>
<html>
<head>
    <title>My Minimal Site</title>
</head>
<body>
    <nav>
        <a href="?page=home">Home</a> | 
        <a href="?page=settings-language">Language</a> | 
        <a href="?page=settings-privacy">Privacy</a>
    </nav>

    <?php
    if ($page === 'home') {
        // Home page content here
    } elseif ($page === 'settings-language') {
        // Language settings content here
    } elseif ($page === 'settings-privacy') {
        // Privacy policy content here
    } else {
        // 404 error content here
    }
    ?>
</body>
</html>

Critical Security Reminder #

Always validate and whitelist user input (like the page or section parameters) to prevent attackers from accessing sensitive files. Never use unfiltered input directly in include or require statements!

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