Skip to main content
drupalreleases

Use direct release data with your AI assistant.

Learn more

System Page Override

Security covered Under active development 41 sites

This module allows site administrators to designate specific content as the front page, or as the 403 (access denied) or 404 (not found) pages directly from the content editing form. These settings are stored separately from configuration imports, which prevents accidental reverts, and can be managed independently for each language and content type.

The System Page Override module allows site managers to set content to be the front page (or the 403 and/or 404 page) directly from their edit form, without the risk of this being reverted on the next config import.

Features

Overrides stored in state (instead of configuration)
When setting a node to be the one of these "system pages", this override is stored in state. The default paths being served on these system pages are saved in configuration. Storing the overrides in state prevents them from being reverted during (automated) configuration imports. This also circumvents issues that occur when referencing content in configuration (e.g. you cannot rely on node IDs).

Overrideable per language
There is multilingual support, so system pages can be configured to differ per language.

Configurable per content type
The node form integration is configurable per content type, per system page. So for example, you can enable site manager to set content from type "page" or "landing_page" to be the front page directly from their edit form, while only content of type "page" can be used as 403 or 404 page.

Fine grained permissions
The node form integration is restricted by a permission. Only users with the "..." permission can override system pages directly from node edit forms.

There also is a system page overrides overview page, only accessible for user with a dedicated permission (administer system page overrides). Users with this permission can also configure overrides other than node pages.

Installation

Usage

  • Install the module as described above.
  • Grant permissions to the desired roles.
  • With the 'Administer system page override settings' and 'Administer system page overrides' permissions enabled, head to Settings > System > System Pages Override > Settings tab.
  • Select which content types should be configurable as system page.
  • Visit a node's edit page that matches one of the enabled types
  • Under the Systempage settings tab, check a checkbox of your liking
  • Submit the edit form
  • That node is now the system page you wanted it to be!
  • To see all overridden system pages, head to Settings > System > System Pages Override > Overview tab.
  • Here all system pages for all languages can be seen and changed.
Drupal 10–11

Ask your assistant about System Page Override

Check compatibility with your Drupal and PHP version, maintenance and security coverage, from current release data. How it works

Depends on

Dependencies of the latest stable release

No dependencies recorded for this project.

Required by

Tracked projects that depend on this one

No tracked projects depend on this one yet.

Activity

Tracked releases
1
Tracked since
Mar 2026
Latest release
7 months ago
Releases (12 mo)
1 ▲ from 0
Maintenance
Slowing

Releases

Version Type Core PHP Release date
2.0.4 Stable 10–11 Mar 9, 2026