TYPO3 Core

I'm not sure how exactly this would help with the usecase described. The only thing that would work reliably here is overriding toplevel form definition properties. As soon as you have renderables keys can be arbitrary (of course identifier s too) which makes it next to impossible to override specific entries.

Hi Bjoern,

i did not solved it for me. I just copies the form and modified the needed keys.

But to catch up Mathias comment i agree on what he said. BUT if we dont need a general overrides feature, why do we have an override for individual form definitions? Because what is true to my addition is also true to the part that is already there.
Once you are in a scope of renderable keys you cant override with $formDefinition['identifier'] anymore too.

For what i needed it was not solved by logic and clever coding but by swapping out templates by changing pathes via typoscript conditions. I still think its a stupid way of doing that but i wasnt willing to carry patches agains the core for that purpose.

If you still have problems with the patch i would like to know what the problem with the patch is. But by know it was only delayed without any good reason. I'd like to bring this issues to a solution but dont realy see what is blocking it.

I put it in your hands. If you think that having the opportunity to override all forms with certain values is less important then overriding values in forms with defined names then drop my request and explain why you dont want to have it in.

Kind regards
Sebastian

In addition: small example what is possible with that patch. You are able to override labels in a multilanguage multitree situation. Define the form once in german and have in a separate english tree different labels.

Or you can override email finisher configuration for development/staging to send the emails to a different testing emailbox then on production environment. For all forms even those that get added by editors in a later project state.

The feature to override specific form definitions with typoscript is thought for integrators that render static forms from their site package.
Since these forms can not be changed by an backend editor, all form elements and their positions are known.
I think an override which applies to all forms for reasons already mentioned above is not helpfull.
We are currently developing a concept for conditional form elements, which should also solve the usecases you described.
In the next few days i will upload a first related patchset.

In the next few days i will upload a first related patchset.

https://review.typo3.org/c/54982/

Looks good to me. So this ticket can be closed in favor of 84133