Bug #18292
closed
Flexforms get mixed up when using sections
Added by emds-itsupport over 16 years ago.
Updated about 11 years ago.
Description
I have created modules which use sections quite extensively.
Although I am not quite sure what the problem is, some fields of my sections get deleted, or duplicated from a same field from the previous section, etc.
I think this problem happens after sorting the sections.
In beta2a, sometimes it is not possible to drag-drop sections for sorting, and when sorting, sometimes it does not do it properly (this also occured in previous version)
(issue imported from #M7648)
Could you please give a short step by step description how to reproduce this issue? Thanks!
I will provide with full example soon, as this one requires more anylsis of the flex, etc.
- Status changed from New to Needs Feedback
- Target version deleted (
0)
Seems to be true when sections are used together with MM relations, since the relation will be made with the "parent" field of the section only, resulting in a change of ALL section elements when changin only one.
Steps to reproduce:
1. Create a flexform with sections
2. Create a select type element within a section and configure it to use MM tables
Now create a new content element using these sections.
You can create as many section elements as you like and select different values for them, but after saving each of them will have got the same value making all the other values disappear.
BTW: It's always the last section value that wins.
So it seems that there is a foreach loop that does not take care of a proper numbering of the sections but sets the value of the parent field instead.
Expected behaviour would be: As many entries in the MM-table as there were sections elements while saving.
Of course technically this has to be impossible without an identifier in the MM table to be able to assign the saved values to the sections when loading the form afterwards.
So it's obvious why this is not working, but IMHO either it should be working or it should be clearly stated that there are some restrictions to the possible setups of flexform fields used in sections.
The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?
- Status changed from Needs Feedback to Closed
- Is Regression set to No
Also available in: Atom
PDF