Posted by phenaproxima on October 15, 2008 at 5:49pm
Jump to:
| Project: | Event |
| Version: | 5.x-2.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
I believe I have discovered a bug in the way Event handles the conversion from the 12-hour to 24-hour time format. I'm not sure where exactly in the code this is happening, but I found that when creating or editing events in 12-hour format, the ending hour would always get set to 24, which in turn would cause MySQL to save a blank date ("00-00-0000 00:00:00", since MySQL datetime fields cannot have "24:00:00" values). Switching the event module to the 24-hour format circumvents the problem. Let me know if you need any more information from me in tracking this issue down...thanks!
Comments
#1
I'm seeing this in Drupal 6.6 with an event snapshot from perhaps June 2009, too.
In my case, the exact steps to reproduce are:
1. Leave 'Event has a time' on.
2. Leave date to default, set time to 12 pm.
3. Leave 'Event has an end date' off, do not touch the dropdowns.
Save and the Start Date will be saved as blank. I cannot reproduce it for times other than 12pm. Switching to 24-hr format avoids the problem.