TYPO3 Core

Now i know that this isn't IRRE. It's Kaspers new flexform arrays, unfortunally this is not documented anywhere.

The attached patch is just a beginning, it adds the flexform sheets/tabs to the stack of nested elements.

• add required-icon to each field of a flexform block
• extend the required nested checks to use flexform sheets (=tabs) and fields
• really remove flexform sections (currently they are only hidden and not removed)
• create a better handling for adding/removing dynamic flexform secions
  -> add: register some stuff in JavaScript
  -> remove: ensure that no other part relies on a removide flexform section

Duplicate of 0013117 witch has some sponsoring

i don't see any sponsoring there ;)

olly did some investigations and i looked to this yesterday too. From my debugs, the flexform field is in the nested stackes. I used this debug in line 202:
if (autoNotify) {
console.log(elementData, elementName);

which showed that the required field in in elementName. Only the elementData is the complete flexform.
Imho this is because of the recursive render of flexforms in t3lib_tceforms.

2 things have to be done:
1) fields in flexform also need the rec_ and cm_ image rendered in front
2) the field has to be added to the stack (see olly's patch)

then the javascript will work as expected and the correct image will be set.

This bug is still present in TYPO3 4.4. The patch is no longer compatible with this version.

When #17122 is fixed, this issue is fixable.

Nothing happend here until today...

We just tested it with the current master and can confirm that this applies also for TYPO3 6.2.

Fields configured with 'eval' is set to 'required' are not marked with exclamation mark and the record can be saved even if the field is not filled with data.

Exception: last input field (see #17122)

It also seems to affect group fields with a configured minitems value.

The FlexForm can not be saved (JavaScript alert about missing fields pops up) but no exclamation mark is visible.

Alexander Stehlik wrote:

It also seems to affect group fields with a configured minitems value.

The FlexForm can not be saved (JavaScript alert about missing fields pops up) but no exclamation mark is visible.

I can confirm this too on TYPO3 6.2.1, but I can see the exclamation marks!
(If I remove the minitems from the flexform, the issue is gone)

Alexander Stehlik wrote:

It also seems to affect group fields with a configured minitems value.

The FlexForm can not be saved (JavaScript alert about missing fields pops up) but no exclamation mark is visible.

I can also confirm this behave of the validation issue with filefields with an minitems of 1. I found another bug #47372 which fixes the same error with TCA-objects, but the fix did not work for flexforms.

Alexander Opitz wrote:

What the state of this issue?
Does it still happen with TYPO3 CMS 6.2.14?

Yes. There was no improvement in TYPO3 6.2 regarding this bug.

this will probably not fixed in 6.2 anymore. there was a lot of effort in 7 to improve the required handling and it is not possible to backport this stuff to 6.2.

verified: this is fixed in 7, but will not be changed in 6.2. i'll close the issue as 'won't fix' for 6.2 now.