Issue Story Closed

#109484SiteSets feel out of place and are too limited for our usecases

Philipp Wrann 04/03/26, 11:25 updated 04/03/26, 14:10

Description

I think the SiteSets need to be partially re-implemented. They feel very alien to everything else and don’t integrate nicely in a working ecosystem.

1) Another descriptive language for Configuration (Besides everything there already is)
2) Translation-Logic is completely out-of-place, reminds me of the arbitrary form-framework (another alien inside typo3) and makes it impossible to re-use existing labels (EDIT: Seems to have been solved in V14)
3) No way of customizing the definitions in the implementation (if one likes it or not, thats the reality)
4) No way of configuration different values for different languages (thats a real requirement imo)

Also – now there are 2 Modules in the Backend both called “Settings”.

Don’t get me wrong, i am very grateful for all the efforts you invest, i am just stating my opinion. I am a TYPO3-Integrator/Developer since Version 4.5, have built more than 100 Websites with it and provided much feedback over the years. Please take this serious. To me the SiteSets / SiteSettings feel like the worst possible implementation for a problem, that did not really exist. The Site Configuration provides much more options and you would have everything in exactly one place. It could have been added in the same way (SiteConfiguration TCA for new node-types) using the same UI-Components. I would have liked that much more.

Please address these issues. My concern is, that we will keep adding things to the Site-Configuration (because it’s objectively better) and you might decide to get rid of all of that in favor of this new “concept” and all of our custom site-config might be broken. If it comes to that, the new system needs to be capable of handling everything we added to the SiteConfiguration so far.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 7

  1. Garvin Hicking commented and changed status New Closed <span data-processor="relativetime" data-value="2026-04-03T14:10:46+00:00" > 04/03/26, 14:10 </span>

    I understand you are frustrated. Two of your issues (#109393 and especially #109305) are valid concerns and should be adressed – thanks for reporting them.

    I am closing this “meta ticket” though because it does not address a way forward with actual changes and the actual issues are existing as separate issues (thanks for linking them). We cannot have issues open that mainly say “don’t change this” or “remove a feature that is working for many people and has just been recently implemented”.

    > I think the SiteSets need to be partially re-implemented. They feel very alien to everything else and don’t integrate nicely in a working ecosystem.

    I strongly disagree with this assessment. Site Sets are meant to replace extension config and extension typoscript constant configuration. The main reason for that is that TypoScript is a very TYPO3 specific configuration syntax. In a world that strives for unification and similar concepts, we have realized that to ush TYPO3 forward and make it accessible to people coming from other systems we need to provide configuration ways that are easier to grasp. A simple YAML configuration was what felt to be usable for most people. It is easily readable, can be parsed with industry standard tools, and is a concept familiar to nearly all web systems.

    We do not want to create frustration for long-time TYPO3 users, which is a reason why old concepts sometimes stick around, and why old extension config and typoscript constants are still around.

    Site Settings are NOT meant to replace Site Configuration. Site Configuration is meant for maintainers and admins, and Site Settings are meant for integrators. (that’s my personal take away).

    Feel free to bring forward actual concepts or even patches to improve your situation (as you did with two issues).

    Other than that I can really recommend you to watch https://www.youtube.com/watch?v=iS4NcYxzjyQ&t=194s for details and backgrounds. If you do not do that, you are not understanding vital ideas and motivation.

    > Also – now there are 2 Modules in the Backend both called “Settings”.

    This is no longer true in TYPO3 v14.

    > My concern is, that […] you might decide to get rid of all of that [SiteConfiguration] in favor of this new “concept”

    We have deprecation and breaking change policies in place. If we address this, it will be part of our public review system and you can participate, as is common in OpenSource projects.