#5448 - Blanking out a date field does not save a blank date
-
By PDStig
- Added
- 2 views
| Identifier | #5448 |
|---|---|
| Issue type | Minor issue (breaks specific functionality) |
| Title | Blanking out a date field does not save a blank date |
| Status | Open |
| Tags |
Roadmap: v11 (custom) |
| Handling member | Chris Graham |
| Addon | General / Uncategorised |
| Description | When blanking out an optional date / time field, it does not save. Instead, Composr maintains the previous value of the field. The expected behavior is that the date/time field would save as blank. |
| Steps to reproduce | |
| Additional information | Be cautious about this because we do not want to save blank dates/times if the post param was not actually specified; we need to ensure it was actually specified as blank and not just excluded as a parameter / field. |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
My attempted method was to alter the API for getting date components so that it returns null for a blank date and false for no date field being provided at all. Unfortunately, this created a mess of type errors and bugs. It also created a cascade effect as altering one API resulted in having to alter several more.