Drupal is a registered trademark of Dries Buytaert
Search API Solr 4.4.0 Minor update available for module search_api_solr (4.4.0). Page Manager 8.x-4.0 Major update available for module page_manager (8.x-4.0). Trash 3.1.0-beta2 New beta version released for module trash (3.1.0-beta2). Commerce AutoSKU 3.0.1 Minor update available for module commerce_autosku (3.0.1). Custom Field 4.0.10 Minor update available for module custom_field (4.0.10). Alternative login ID & display names 2.0.12 Minor update available for module alt_login (2.0.12). EntityReference UUID 3.0.1 Minor update available for module entity_reference_uuid (3.0.1). LocalGov Publications Importer 1.1.1 Minor update available for module localgov_publications_importer (1.1.1). Configuration Override Warn 8.x-1.6 Module config_override_warn updated after 10 months of inactivity (8.x-1.6). Table Alternate Rows Module table_altrow crossed 1,000 active installs.

System Page Override

26 sites Security covered
View on drupal.org

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.

Activity

Total releases
1
First release
Mar 2026
Latest release
4 months ago
Releases (12 mo)
1 ▲ from 0
Maintenance
Active

Releases

Version Type Release date
2.0.4 Stable Mar 9, 2026