The old functionality of "notification dates", "past dates" and "normal dates" is not working anymore and even wrongly restructured.
I believe that the one who redesigned the field did not understand the behaviour of the field.
Please see screenshot how it should work and worked since cobalt 7 and before as terix_date field for mighty resources.
Dates should be displayed in normal color, if they are not expired. Displayed in "notification color", if they are due in XX days (defined in the field parmeters) and displayed in "past color" if they are expired.
One of the problems of this field was the correct computation of the behaviour of the actual date, based on the field value. The date is normally stored as 2012-12-12 00:00 --> therefore the actual date is considered already expired the moment it starts. To adjust properly to this behaviour, parameters like ceil(), floor(), +1 etc were introduced, but never implemented.
The good thing on the update is, tht the datepicker/manual input error was addressed. But overall this field is not useable anymore, if a user wants the notification and styling of different date states.
See OLD field behaviour in following screenshot
Assuming that today is 15/02/2013 see the wrong computation for today , but the different coloring for the 3 display states (valid/soon to expire/expired)
In the NEW field, all dates are displayed in the same color as selected in the field definition.
To get the old definition back into the new field, we have to write our own output template, where this functionality was part of the old core date field.
Problem
Announcement
Conversation
Idea
Praise
Question
Open
The old functionality of "notification dates", "past dates" and "normal dates" is not working anymore and even wrongly restructured.
I believe that the one who redesigned the field did not understand the behaviour of the field.
Please see screenshot how it should work and worked since cobalt 7 and before as terix_date field for mighty resources.
Dates should be displayed in normal color, if they are not expired. Displayed in "notification color", if they are due in XX days (defined in the field parmeters) and displayed in "past color" if they are expired.
One of the problems of this field was the correct computation of the behaviour of the actual date, based on the field value. The date is normally stored as 2012-12-12 00:00 --> therefore the actual date is considered already expired the moment it starts. To adjust properly to this behaviour, parameters like ceil(), floor(), +1 etc were introduced, but never implemented.
The good thing on the update is, tht the datepicker/manual input error was addressed. But overall this field is not useable anymore, if a user wants the notification and styling of different date states.
See OLD field behaviour in following screenshot
Assuming that today is 15/02/2013 see the wrong computation for today , but the different coloring for the 3 display states (valid/soon to expire/expired)
In the NEW field, all dates are displayed in the same color as selected in the field definition.
To get the old definition back into the new field, we have to write our own output template, where this functionality was part of the old core date field.