Silverstripe v4 MVC目录疑问：为何无MVC目录及如何实现MVC风格

Great question! Silverstripe 4 moves away from the rigid Models/Views/Controllers directory structure you might see in other MVC frameworks, but you can absolutely build a clean, MVC-aligned setup using its namespace and PSR-4 autoloading system. Let’s walk through how to do this within the default mysite/code directory (or even customize it further).

1. Organize Your Directory Structure #

Start by creating subdirectories inside mysite/code to mirror MVC components. Here’s a standard, maintainable setup:

• Models/: For your data models (classes extending DataObject or Page)
• Controllers/: For your request handlers (classes extending Controller, PageController, etc.)
• Views/: For custom view logic (like helper classes, renderers—note: Silverstripe’s template files live separately in the templates/ folder)

Example Namespace & Class Setup #

For a Product model in mysite/code/Models/Product.php:

namespace MySite\Models;

use SilverStripe\ORM\DataObject;

class Product extends DataObject {
    private static $db = [
        'Title' => 'Varchar',
        'Price' => 'Decimal'
    ];
    // Add validation, relations, or other model logic here
}

For a corresponding ProductController in mysite/code/Controllers/ProductController.php:

namespace MySite\Controllers;

use SilverStripe\Control\Controller;
use MySite\Models\Product;

class ProductController extends Controller {
    // Define allowed public actions
    private static $allowed_actions = ['show'];

    public function show($ID) {
        $product = Product::get()->byID($ID);
        if (!$product) {
            return $this->httpError(404, 'Product not found');
        }
        // Render with a custom template + fallback to Page layout
        return $this->renderWith(['Product_show', 'Page']);
    }
}

2. Handle Views (Templates & View Logic) #

Silverstripe separates template files from PHP view logic for better separation of concerns:

• Template files: Live in the templates/ directory, structured to match your namespaces. For the Product_show template above, create templates/MySite/Views/Product_show.ss (stick to a consistent pattern, like mirroring your code directory structure). Example template content:

<div class="product-detail">
    <h1>$Product.Title</h1>
    <p class="price">$Product.Price.Nice</p>
    <% if $Product.Description %>
        <div class="description">$Product.Description</div>
    <% end_if %>
</div>

• Custom view logic: If you need reusable view helpers (like formatting functions or complex rendering logic), put them in mysite/code/Views/. For example:

namespace MySite\Views;

class ProductViewHelper {
    public static function formatPrice($price) {
        return '$' . number_format($price, 2);
    }
}

You can use this helper in templates by passing it via your controller’s data or registering it as a global helper.

3. Configure Custom Routes (If Needed) #

If your controller isn’t tied to a Page type (e.g., it’s a standalone API or custom page), add a route in mysite/_config/routes.yml to map URLs to your controller:

SilverStripe\Control\Director:
  rules:
    'product/$ID': 'MySite\Controllers\ProductController->show'

This will make yoursite.com/product/123 load the show action with ID=123.

4. Optional: Customize Your Root Code Directory #

If you don’t want to use mysite/code, you can rename it (e.g., to app) by updating your composer.json PSR-4 autoload config:

"autoload": {
    "psr-4": {
        "MySite\\": "app/"
    }
}

Run composer dump-autoload in your terminal to update the autoloader, then adjust your directory structure accordingly.

Key Takeaway #

Silverstripe 4 doesn’t enforce a strict MVC folder structure, but it gives you full flexibility to implement one using namespaces and autoloading. The core idea is to align your directory structure with your namespaces—this ensures Silverstripe can autoload your classes and find your templates correctly, keeping your code organized and maintainable.

内容的提问来源于stack exchange，提问作者Mr.Online