When adding/editing an event, if the date and time set in the "End date" fieldset would occur before the date and time set in the "Start date" fieldset, the "End date" values are all reset to zero and the event doesn't show up in the calendar. To fix this, the user must edit the event and set the date and time in the "End date" fieldset to come after the date and time set in the "Start date" fieldset.
When viewing/editing the event, it may show a value equivalent to zero in some places. For example, the time may be displayed as "12:00 AM" if using the 12-hour notation (which is the same as "0000" in the 24-hour notation). When editing the event, if a value equivalent to zero isn't available, the lowest non-zero value will be used in its place (and may still show a zero value for that field when viewing that page). For example, if a select box is used for the month, it would default to "January", even if the value for the month when viewing the event shows up as zero.
Would there be a way to prevent the user from submitting an event (or changes to it), as well as showing them an error message regarding this, until they fix the date and time in the "End date" fieldset?
Comments
Comment #1
Mac Clemmens commentedYes, I'm having the same issue. Thanks for describing it so well.
Comment #2
killes@www.drop.org commentedI can't reproduce this. If I enter an event with a start date today and an end date on 1st November, the end date will be equal to the start date on submission.
Comment #3
Wolfey commentedWith the most recent "dev" release for Event, these issues no longer occur. As you mentioned, if the end date comes before the start date, it will be made equal to the start date (and show up on the calendar), rather than be replaced with zeros (and not show up on the calendar).
It appears this issue has been fixed =)
Comment #4
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.