[SOLVED] It has gotten out of control (configuration languages)

TYPO3 Questions
1

I recently started to add V13 support to all my products, packages and projects. Late? Yes, but TYPO3 breaks so many things in every major release, that we simply can not keep up the pace.

Nevermind - my concern is about the current configuration situation in TYPO3. We went from having basically 2-3 configuration languages and storage formats (typoscript/tsconfig and php/tca) to about 8+ different configuration languages.

  1. typoscript for frontend config and rendering

  2. typoscript constants - to basically have backend-ui support for those frontend-settings

  3. site settings with a new yaml-syntax for frontend config (??? don’t we have constants already?)

  4. site config yaml with underlying pseudo-tca for … frontend/backend config on site-level

  5. tsconfig for backend config and backend customizations

  6. tca for schema config

  7. form framework yaml … shitshow (can’t call it differently, i hate it with a passion)

  8. vanilla php configuration in various places of course

  9. and there is the extension configuration as well, also with its own syntax

That’s the situation. Is it good? No, IMO it’s horrible! It seems like there is absolutely no concept. Why do we need so many different configuration languages and configuration storage formats, why can’t we live with the ones, we already had? Bringing typoscript support to the site-config would have also brought constants support and therefore backend-ui support as well, why introduce the new site settings?

I get it - we all like shiny new things - but that kind of development can kill a product like TYPO3. TYPO3 should not try compete with newest shiniest things out there (a battle, that a php-based cms won’t be able to win), TYPO3 is what it is because it brings over 20 years of experience, of battle-proof hardened patterns. TYPO3 gets everything done, no matter the requirement, its safe, its open, its great. We still love it!

Is there a task to streamline/simplify the configuration for TYPO3?

2

Also - the Site Settings lack any support for translation handling, some features, where a setting needs to be different depending on the language (date format, editable labels, etc), can only be configured in the site config or page tree.

3

Hi @majpay!

Streamlining configuration is an ongoing process and establishing new best practices takes time.

There aren’t eight different configuration languages, of course, but configuration for different things are kept separate. I think that’s generally good, though some openings for legacy configuration also needs to be kept in place to give some backwards compatibility and cover certain use cases.

That means API and configuration streamlining in itself may require you to change your code. However, a lot of the job has been solved with some great tools. Have you tried Rector and Fractor for TYPO3? They make code and configuration much easier to upgrade.

I think it’s a great idea to add stuff like date format in the translation handling! If it’s not already there, I think you should submit a feature request.

There are many ways to sell TYPO3. Both experience and shininess are important for different target groups and markets. Feel free to join the TYPO3 Marketing Team to help shape how the story is told.

4

Thank for your response. I will definitely have a look at the tools you mentioned. The feature request is submitted as well: Making sure you're not a bot!

1 Like