[TYPO3-dev] Flexforms overriding TS in Extbase Extensions

[Bastian Waidelich]

Thomas Allmer wrote:

Hi Thomas,


>> Bastian's proposal was to change the whole Flexform mechanism so that an
>> input field can have e.g. a checkbox in front of it to NULL it out or
>> something like this.

> oh not another hard to get extra setting box... :/

It doesn't have to be a new setting box. Especially no "hard to get"-one ;)
It could even be an extended variant of the already existing "default" 
setting, like:
[...]
'config' => array(
	'type' => 'input',
	'default' => NULL,
)
[...]

That would be displayed as before, but avoid the field from being 
transmitted when the little "x" is clicked.
That could be a clean solution for type "input" at least..


> I'm pretty sure it's not easy doable but for me the perfect solution
> would be to just display the current ts setting inside the flexform.

would clutter the flexform with unneeded values and that would have 
quite some side effects. E.g. when you change the default value of a ts 
setting *afterwards*.


> With that if the value is empty in ts it will be empty in the flexform

I see, you would not set the FF field if it was the same as the default 
value?
That would still have the mentioned side effects: if a user sets it 
explicitly to the same value it will be changed as soon as the default 
value is changed.. Maybe that's an acceptable side effect though!?

> and if it's set with something the editor even sees it and can change it
> if needed.

That would be a nice feature indeed..

Anyways, as far as I'm concerned I could close the Extbase issue as this 
seems to be an issue that affects others too and that should be dealt 
with in the core.

Best,
Bastian