Open dmolineus opened 7 years ago
Should be fixed in f2589769bff2ad82ef2d7aed127451a693b254ee or not?
Probably dupe of #383
@discordier was hat # 383 mit doNotSaveEmpty zu tun?
Should be fixed in f258976 or not?
Unfortunately not. The extra param doNotSaveEmpty
is simply not handled anywhere in DCG. Afaik it wasn't available in Contao when DCG was intial created. So I guess that's why it's missing at the moment.
@zonky2 sorry, I mixed up alwaysSave
and doNotSaveEmpty
@zonky2 Can you test this. I mean is so good.
Zum Beispiel für Passwortfeld oder ein Feld, was nie leer werden darf...
Checklist before I submit this issue report
I confirm that:
My environment is:
(Please fill in the actual values from your environment)
Issue description
I stumbled upon the issue that a wrong default value is used (MM 2.1 context) and the DB saving failed. I had a closer look, the field should actually not be saved when being empty (
doNotSaveEmpty
). I checked the source code of the DCG, there is not checking of the flag in the DCG at all.I think it should be added to the DefaultDataProvider. But the definition is not available there. Any ideas how to solve it @baumannsven @discordier?