#109805[Feature] Site Settings Modal triggered from content element / plugin context
Description
Problem / Motivation
Site Sets (introduced in v13.1) allow extensions and site packages to define global configuration values via settings.definitions.yaml. These settings often directly control the behaviour and appearance of specific content elements and plugins (e.g. animation speed, colour scheme, API endpoints).
Currently there is no UI affordance that shows a backend user — while editing a content element or plugin — that global site-level settings exist and affect this element. The editor must navigate manually to Site Management → Settings, find the correct category, and identify the relevant keys. This creates unnecessary friction and makes the settings system opaque for integrators and editors alike.
Proposed Solution
Introduce a mechanism that allows a content element or plugin to declare which Site Settings categories or keys it depends on. When a backend user edits such a record, a contextual button appears in FormEngine that opens a filtered Site Settings modal — showing only the relevant settings for that element, editable inline without leaving the current view.
The modal reuses the existing Site Settings Editor FormEngine output, filtered by the declared keys or category. No new editing infrastructure is needed.
Proposed API
Content Blocks (EditorInterface.yaml)
name: myvendor/hero-element
fields:
- identifier: header
type: Text
siteSettings:
category: myvendor.hero
# alternatively, explicit keys:
# keys:
# - myvendor.hero.colorScheme
# - myvendor.hero.animationSpeed
Raw TCA
$GLOBALS['TCA']['tt_content']['types']['myvendor_hero']['ctrl'] = [
'siteSettingsReference' => [
'category' => 'myvendor.hero',
// or: 'keys' => ['myvendor.hero.colorScheme', 'myvendor.hero.animationSpeed'],
],
];
Expected Backend Behaviour
When siteSettingsReference is declared on a CType, FormEngine renders a fieldInformation node at the top of the element form. This node displays a button labelled “Global settings” (or similar, translatable via XLF).
Clicking the button opens a native TYPO3 backend modal containing only the Site Settings fields matching the declared category or keys for the current page’s site. The user can edit and save without leaving the content element context.
Technical Notes
- Site is resolved at runtime via
SiteFinder::getSiteByPageId($pid)from the current record’spid. - Modal renders the same FormEngine output as the existing Site Settings Editor, filtered by the declared keys.
- Save action writes to
config/sites/<identifier>/settings.yamlvia the existing Site Settings save endpoint — no new persistence logic required. - Access is gated by the same permissions as the Site Settings Editor (admin-only in v13/v14; can be relaxed in a follow-up once core opens the module to non-admin editors — as already noted in the v13.3 changelog).
- Content Blocks passes the
siteSettingskey fromEditorInterface.yamldirectly into the generated TCActrlarray. - No changes required for elements that do not declare
siteSettingsReference.
Acceptance Criteria
- Declaring
siteSettings.categoryorsiteSettings.keysinEditorInterface.yamlautomatically generates a “Global settings” button in the FormEngine record form. - The button opens a modal showing only the declared settings for the current page’s site.
- Settings can be saved from the modal without a full page reload.
- Works with Content Blocks and raw TCA equally.
- No regression on content elements without
siteSettingsReference.
Related
- Feature #103437 — Introduce site sets
- Feature #104794 — Site Settings Editor
- EXT:content_blocks (Content Blocks extension)
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Files 1
History 2
-
Georg Ringer commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2026-05-09T11:51:09+00:00" > 05/09/26, 11:51 </span> -
Georg Ringer commented and changed status
Needs FeedbackClosed <span data-processor="relativetime" data-value="2026-10-07T18:07:52+00:00" > 10/07/26, 18:07 </span>closing the issue because lack of feedback. if still relevant, please open a new issue or contact me on slack to discuss.
thanks for the idea. I don’t really get why the editor should know about those features as an editor is also not the target group of site settings and can’t even edit those – otherwise it would be a site administrator.
If you really need to show this information I suggest using formengine’s nodes and provide that additional information to the editor with that – but I currently see no need in the core.