Setting a value always resets the field on mapping errors
|Status:||Under Review||Start date:||2012-02-22|
|Priority:||Should have||Due date:|
|Assignee:||Sebastian Kurfuerst||% Done:||
|Has patch:||No||FLOW3 version affected:||Git 1.0|
If I set a value on any field of the form it gets reset every time there
is a mapping error, so the user has to reenter the field every time.
Could easily be fixed by changing the order of the if-clause in
|duplicated by TYPO3.Fluid - Bug #47363: Error Classes are only set for form fields in object context||Under Review||2013-04-18|
Updated by Kira Backes about 1 year ago
Okay, it’s not that easy to just change the if-else order, then submit buttons disappear.. I guess we need another attribute for a start value like that or we only use the submitted form data if it is not NULL.
Updated by Bastian Waidelich about 1 year ago
Please provide more information. Did you use one of the form viewhelpers (which one?) and bind it to a property of the form object? Can you provide some (fluid) code snippets?
Updated by Sebastian Kurfuerst about 1 year ago
- Status changed from Needs Feedback to Accepted
- Assignee set to Sebastian Kurfuerst
OK; the automatic fill-in does is partly broken when not using object accessor mode.
Fix is underway.
Updated by Gerrit Code Review about 1 year ago
- Status changed from Accepted to Under Review
Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/10732