#109484SiteSets feel out of place and are too limited for our usecases
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.