Bug #101476
closedFlexform type check does not store values
100%
Description
If I create a FlexForm with an input type check, the value of the flexform is not stored in tt_content:
<T3DataStructure>
<sheets>
<sDEF>
<ROOT>
<sheetTitle>Sheet Title</sheetTitle>
<type>array</type>
<el>
<input_2>
<label>Check</label>
<config>
<type>check</type>
<items type="array">
<numIndex index="1" type="array">
<label>activateLink</label>
</numIndex>
</items>
<default>0</default>
</config>
</input_2>
</el>
</ROOT>
</sDEF>
</sheets>
</T3DataStructure>
The inpot stays "unchecked"
Tested with TYPO3 12.4.4 and styleguide ext
Files
Updated by Torben Hansen 10 months ago
- Status changed from New to Needs Feedback
I'm not able to reproduce the problem. Please verify you have the latest version of ext:styleguide for TYPO3 12.4.
The shown FlexForm seems incomplete to me, since no value
is set.
Example from current ext:styleguide (notice the empty value
node):
<checkbox_1> <label>checkbox_1 one checkbox with label</label> <config> <type>check</type> <items type="array"> <numIndex index="0" type="array"> <label>foo</label> <value></value> </numIndex> </items> </config> </checkbox_1>
I also tested some extensions that use FlexForm with checkbox fields available for TYPO3 12.4 and could not verify any problems.
Updated by Stefan Busemann 10 months ago
- % Done changed from 0 to 100
can be closed. ich will try to create a PR for the missing documentation about the <value> tag.
in the naked test setup it works the value tag.
In my Powermail dev setup the checkbox does not work yet. Maybe there is another issue.
Updated by Stefan Busemann 10 months ago
Documentation PR is created: https://github.com/TYPO3-Documentation/TYPO3CMS-Reference-TCA/pull/750/files
Updated by Christian Kuhn 7 months ago
- Status changed from Needs Feedback to Closed
Hmm.
I played around on this styleguide elements_basic flex_1 check_1, both creating a new record and changing an existing one. The boxes were checked correctly. styleguide does not add a 'value' tag, either.
We did had a couple of fixes regarding 'value' handling in this area, though ... maybe this was fixed somehow?
I hope it's ok to close here, since I think this was indeed a bug Lina suggested.
Let's have a fresh issue or re-open in case we still missed something.