Bug #72302
closedFlexform writing / reading inconsistent
0%
Description
Try the following:
1) Create a flexform with 2 sheets, insert some field in the second sheet and save the value.
2) Change the flexform and move the field to the first sheet (because displayconditions do not work in the second sheet :-/ )
3) Change the value of the field in the new position (sheet)
4) Open the record -> the data is displayed correctly but if you look it up in the database or the frontend (via extbase controller-settings) the value is not the same
It seems data is looked up in the correct sheet when displaying the flexform - but it is merged pretty brutally when evaluated as php array.
Did using flexforms become deprecated or how can it be that there are so many bugs lately?
A) This should be fixed on the write-side, if some field does not exist in the flexform source it should be filtered before it is saved as xml
B) Maybe the time has come to think about something better than flexforms for the future? Just sayin - sDEF/lDEF/vDEF - OUT
Updated by Morton Jonuschat almost 9 years ago
- Category changed from FormEngine aka TCEforms to DataHandler aka TCEmain
- Status changed from New to Closed
- Target version deleted (
7 LTS)
Hi Philipp,
the situation you describe is how FlexForms have always worked in TYPO3, fields no longer present in the data structure don't get removed automatically. There is an option to clean the XML which - if I remember correctly - can be triggered from the lowlevel_cleaner task using cli_dispatch.phpsh.
Regarding your point 2) please open a dedicated issue for that and provide a sample flexform that includes the failing displayCond, I tried conditions in multiple sheets and failed to reproduce the issue.
Thanks