Silverstripe Elemental模块保存元素跳转404及编辑器异常求助

Let’s break down your two problems and walk through targeted fixes—they’re likely tied to namespace inconsistencies or extension configuration quirks common in early Silverstripe 4 setups.

Problem 1: Saving an Element Redirects to Frontend 404 #

This happens because the CMS can’t resolve the correct backend edit route after saving an element, so it falls back to the frontend page URL (which may not exist or be published yet). Here’s how to fix it:

1. Fix Namespace Case Mismatch #

Looking at your code, there’s a critical case inconsistency in your namespaces:

• Your model uses XYPage\Model\HomePage (capital "P" in XYPage)
• Your controller uses XYpage\Controller\HomePageController (lowercase "p" in XYpage)

Silverstripe is case-sensitive with namespaces, so this breaks route resolution. Fix the controller’s namespace to match:

namespace XYPage\Controller; // Capital "P" to match model namespace
use PageController;
class HomePageController extends PageController {}

Update the model’s controller reference too:

namespace XYPage\Model;
use Page;
use XYPage\Controller\HomePageController; // Updated to match fixed namespace
class HomePage extends Page {
    private static $table_name = 'HomePage';

    public function getControllerName() {
        return HomePageController::class;
    }
}

2. Verify Extension Configuration #

Double-check your config.yml to ensure the class name matches the corrected namespace (case-sensitive):

XYPage\Model\HomePage:
  extensions:
    - DNADesign\Elemental\Extensions\ElementalPageExtension

3. Flush Cache #

Run this command to clear Silverstripe’s config and route caches:

vendor/bin/sake dev/build flush=all

Problem 2: WYSIWYG Editor Disappears After Saving #

This usually stems from missing editor initialization or broken data association between the element and page. Try these steps:

1. Ensure Correct Template Rendering #

Make sure your HomePage.ss template includes the $ElementalArea variable without overriding its default behavior. A minimal template should look like:

<% include Header %>
$ElementalArea
<% include Footer %>

2. Check for JS Errors #

Open your browser’s developer console (F12) when editing an element. If you see errors related to TinyMCE or missing scripts:

• Reinstall Elemental dependencies to ensure all assets are present:

  composer update dnadesign/silverstripe-elemental
  

• For default content elements, confirm you have the dnadesign/silverstripe-elemental-content module installed (it’s required for the basic WYSIWYG element in 2.x):

  composer require dnadesign/silverstripe-elemental-content
  

3. Confirm Element Field Configuration #

If you’re using a custom element, ensure your getCMSFields() method properly initializes the WYSIWYG field. For example:

public function getCMSFields() {
    $fields = parent::getCMSFields();
    $fields->addFieldToTab('Root.Main', HTMLEditorField::create('Content', 'Content'));
    return $fields;
}

4. Flush Cache Again #

Run the flush command once more to apply all template and config changes:

vendor/bin/sake dev/build flush=all

Bonus: Consider Version Compatibility #

Silverstripe 4.0.1 is a very early release of SS4, and Elemental 2.x-dev may have untested edge cases with it. If the above fixes don’t work, consider upgrading Silverstripe to a more stable 4.x release (like 4.13.x) which has better compatibility with Elemental’s later 2.x or 4.x versions.

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