View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0027950 | mantisbt | custom fields | public | 2021-02-06 06:58 | 2021-03-07 18:28 |
Reporter | dregad | Assigned To | dregad | ||
Priority | normal | Severity | minor | Reproducibility | N/A |
Status | closed | Resolution | fixed | ||
Target Version | 2.25.0 | Fixed in Version | 2.25.0 | ||
Summary | 0027950: Validate date custom fields default value format | ||||
Description | Currently, users can store anything in the default value field for date custom fields, including invalid date formats which are then silently ignored when calculating the actual date value, resulting in an empty date field. | ||||
Tags | No tags attached. | ||||
MantisBT: master efd8d1fb 2021-01-31 04:00 Details Diff |
Validate date custom fields default value format Prior to saving the custom field's definition, we try to convert the provided format to a date, and if that fails an error is thrown. This also removes the need to enclose the format within curly brackets (e.g. {tomorrow}); this is more user-friendly, and simplifies the code as the given value can be passed on as-is to DateTime transformation. Backwards-compatibility is maintained for now, but may be removed in a future release. Fixes 0027950, 0027956, 0027983 |
Affected Issues 0025981, 0027950, 0027956, 0027983 |
|
mod - core/cfdefs/cfdef_standard.php | Diff File | ||
mod - core/custom_field_api.php | Diff File | ||
mod - docbook/Admin_Guide/en-US/Customizing.xml | Diff File |