#109393Provide PSR-14 Event to manipulate Options of "Enum" Site-Settings
Description
I would like to migrate Features from the Site Configuration to the Site Settings. I like the basic concept of Site Settings very much but they are currently extremely limited.
I already created this issue: ##109305
In this issue i would further request a PSR-14 Event, that provides a possible “Hook” for Manipulation of the available “enum” options. I think this will be a common requirement and a event would prevent Extension Authors from sticking to Site Configuration or registering “XCLASS” implementations.
A use case:
I provide a Site-Set to configure the Defaults for Content Elements. For example: When content XY uses the default “frame_class” configuration, what value should be exposed in API or used in Fluid Templates. The available frame_class options are very commonly extended in the implementation and therefore being able to extend the available options via a event would be nice.
In general – when adding new features as successors of existing features – i would try to NOT narrow down the feature set too much, being able to customize TYPO3 the way you need to, is one of the greatest strengths of TYPO3.
Adding a Event should not hurt too much, the person registering the Listener is responsible for the stability, so this would not harm the core functionality/stability.
I would love to see this backported to V13 as well because we are just updating our product stack to V13 and these missing features really prevent us from modernizing.
I did not re-evaluate in V14, if this has been already done, the issue should be re-created as a request to backport it.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 1
History 6
-
Garvin Hicking commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2026-03-27T16:35:06+00:00" > 03/27/26, 16:35 </span> -
Philipp Wrann commented <span data-processor="relativetime" data-value="2026-03-30T11:45:19+00:00" > 03/30/26, 11:45 </span>
I already tried to explain:
> I provide a Site-Set to configure the Defaults for Content Elements. For example: When content XY uses the default “frame_class” configuration, what value should be exposed in API or used in Fluid Templates. The available frame_class options are very commonly extended in the implementation and therefore being able to extend the available options via a event would be nice.
Lets try to re-phrase this:
My plan was: by including the Site-Set “Configure Defaults”, our first-level-support would be able to configure the default behaviour for certain settings per site. Our goal is to avoid coding if reasonable configuration can be applied. One example was the frame_class setting for content elements. If nothing else is selected, the field holds an empty string. And i want to be able to use a configurable setting, that will be used in that case. On site-a an empty string would result in “contain” and in site-b an empty string would result in full-width. Our module comes with some options to chose from (and the used renderer needs to consume them) but often the customers need custom options like contain-small or container-wide.
In the typoscript-fluid-frontend code it looks about like this:
lib.contentElement { variables { containerClasses = COA containerClasses { key.field = frame_class # you get it... } } } tt_content.special_type.variables.containerClasses.key { ifBlank.data = sitesettings: vendor.elements.special_type.defaults.frameClass }We don’t want to need to customize templates/css/whatever (mainly because junior-devs will mostly chose the wrong path), we want to be able to configure defaults for certain things in the backend. We use TYPO3 as backend engine for a page-builder, that our customers use to configure many many websites of theirs.
If you tell me this won’t happen, we won’t use the site-settings for this. But what then? Moving that part to the Site-Configuration? Bad choice, i am about 100% sure you will ditch SiteConfiguration TCA with your new limited yaml style in the future. The next best option is TCA and make it live in the page-tree. Possible? Yes but then all configuration is part of the model and hard to share, i don’t like that.
> Have you watched https://www.youtube.com/watch?v=iS4NcYxzjyQ&t=194s ?
No and i won’t for now sorry i am getting paid to use TYPO3 as a tool to provide the best possible UX for our customers, not as a philosophy ;).
> That explains pretty well why we decided to “limit” the settings definitions to be a central source of truth.
IMO A definition file can not be a source of truth, only the state can be the source of truth and that would be the settings.yaml in the configuration folder.
-
Garvin Hicking commented and changed status
Needs FeedbackNew <span data-processor="relativetime" data-value="2026-03-30T12:39:45+00:00" > 03/30/26, 12:39 </span>Could you not properly “maintain” the frame_class enum settings then? That would make it authoritative.
However:
Quotes like “Bad choice, i am about 100% sure you will ditch SiteConfiguration TCA with your new limited yaml style in the future.” don’t make me want to engage with you. I am out of this thread now. I am doing this on my free and spare time and don’t need to get talked down by you like this when I offered insights or help or questions.
Have a goot time, enjoy life. It’s too short.
-
Philipp Wrann commented <span data-processor="relativetime" data-value="2026-03-31T07:13:23+00:00" > 03/31/26, 07:13 </span>
> Could you not properly “maintain” the frame_class enum settings then? That would make it authoritative.
The projects are composed of modules and implementation, the modules define the defaults and the implementation might require custom values.
@ghi I am sorry, i did not want to offend you in any way. I used “you” to speak about the core development, not you in person. I am very grateful for the work and effort you invest. Again: Sorry.
-
Philipp Wrann changed Related to #109484 <span data-processor="relativetime" data-value="2026-04-03T11:26:17+00:00" > 04/03/26, 11:26 </span>
-
Oliver Bartsch commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-11-17T21:11:34+00:00" > 11/17/26, 21:11 </span>Hey,
this is a feature request rather than a bug, and I’m closing it. Setting definitions, including their enum options, are meant to be the single declarative source for a setting. They are read from settings.definitions.yaml, cached, and are not changed at runtime. A PSR-14 event that rewrites them would undo that, and it is not something we could backport to v14, / v13 either, since only bug fixes go into the LTS branches.
Your use case still works without an event. Definitions are merged by setting key in set order, with dependencies loaded first and the last definition winning. So the project set that depends on your module set can declare the same setting again (e.g.
vendor.elements.special_type.defaults.frameClass) with an extendedenumlist, e.g. addingcontain-smallandcontainer-wide. The site settings editor and thesitesettings:getData lookup then use the project’s options. The project-specific values then live in the project set, next to the frame_class TCA/TSconfig additions they belong to.If that doesn’t work for a concrete setup, please open a new issue with the two set definitions and what you see.
Cheers, Oli
Have you watched https://www.youtube.com/watch?v=iS4NcYxzjyQ&t=194s ?
That explains pretty well why we decided to “limit” the settings definitions to be a central source of truth.
Providing such an event would defeat the purpose of having a single authoritative settings.definitions.yaml file.
Could you maybe describe more in depth how frame_class (TCA) is affected by a site setting? I’m not yet getting the use case to be honest. Wouldn’t that be more related to TSConfig, which is already extensible via extensions?