Events converted from 4.5 have ending timestamps of 0. New events might have unknown or indeterminate end times - without a way to explicitly express this, it seems best to leave the end date at its default, or equal to the start time. In any of these cases, displaying the end time is unhelpful.

I suggest that whenever the end time is <= the start time, the end_format be set to an empty string, and that theme_event_nodeapi skip displaying the end when end_format is empty.

Comments

crunchywelch’s picture

crunchywelch commented
Assigned: Unassigned » crunchywelch

I think the proper behaviour is to set the end time to the same as the start time, and if they are equal do not display them which is the current behaviour when creating new events now. This will be done soon.

crunchywelch’s picture

crunchywelch commented

done in 4.6 branch and head

Anonymous’s picture

(not verified) commented