View Issue Details

IDProjectCategoryView StatusLast Update
0027950mantisbtcustom fieldspublic2021-02-21 11:04
Reporterdregad Assigned Todregad  
PrioritynormalSeverityminorReproducibilityN/A
Status resolvedResolutionfixed 
Target Version2.25.0Fixed in Version2.25.0 
Summary0027950: 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.

TagsNo tags attached.

Relationships

related to 0027956 resolveddregad Remove need to use {} for dynamic dates in custom fields default value 
related to 0027983 resolveddregad Improve Custom Fields documentation 

Activities

Related Changesets

MantisBT: master efd8d1fb

2021-01-31 09:00:39

dregad

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
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