flux:form.section not working for Typo3 7.4

[mkoehler2911]

I tried to create a FCE with flux:form.section. I can add elements but if I save the object my changes won't be saved (the object is created but the content got lost).

I checked the DOM of my backend:
The created object is outside of t3-form-field-container-flexsection t3-flex-container ui-sortable (the div that includes the objects) until I save the FCE.

Any solutions for that?
I found a similar problem in #841

<flux:form id="element" label="MyElement" options="{icon: '', group:'FCEs'}" >
        <flux:form.section name="fields" label="Fields">
            <flux:form.object name="content" label="Content">
                <flux:field.input name="name" label="Name" />
                <flux:field.input name="linkTarget" label="Target">
                    <flux:wizard.link label="Link" />
                </flux:field.input>
            </flux:form.object>
      </flux:form.section>
</flux:form>```

[cdominpxp]

Same problem here: Typo3 7.5.0, Flux 7.2.3, Fluidcontent 4.3.2.
Content get lost after first save if i add new elements.

[NamelessCoder]

Sorry guys, I have to refer you to the TYPO3 core bug tracker.

• We intentionally don't manipulate the HTML that is generated; this is done 100% the TYPO3 core. If it has nesting issues that's absolutely a TYPO3 issue.
• There's a known issue with wizards (flux:form.object don't work in Page Configuration with Typo3 7.2 #841) and a suggested fix; if you can, please help take care of that one.
• Content lost (from FlexForm sections) can be caused by inheritance (every time we speak of inheriting sections and objects, we add a warning that it may not work as intended) or may be related to field name issues (for example, JS failures in TYPO3 backend caused by invalid field naming in DOM output).

The recent changes in the TYPO3 core concerning form rendering has caused us to receive a lot of reported issues about errors which are not caused by FluidTYPO3. The best we can do in these cases is try to add compatibility handling, or refer to the TYPO3 core bug tracker when no solution is possible from our side. In this case there is no solution we could implement.

Cheers,
Claus

[cweiske]

I've opened a bug for TYPO3 core; https://forge.typo3.org/issues/71322 -
Flexform: section contents not saved on first save