Hello Decisions,
I have a problem when trying to schedule a decision for midnight, or 0:00 (military time), or 12:00am (12-hour time).
When I select 12:00am for the opening date, and 12:00am of the next day for the closing date, and then click Save, the decision's opening date is changed to 12:00 military time (which is 12:00 PM = noon) and closing date of 12:00 military time (which is 12:00 PM = noon); not midnight.
I also tried to set the dates to 12:00am to 12:01am, and it just automatically changes it to 12:00 military time and 12:01 military time (so both at lunch time).
The closest time I can set to midnight is 1:00am to 1:00am which does work for some reason. If I set it to 11:59pm to 11:59pm, which is 1 min before midnight, the page reloads with 11:59 military time to 11:59 military time, which is 1 min before before noon!!
So it's almost like the "am" and "pm" radio select options are broken and we are therefore missing hours 13-23, and the hour "0".
One thing I am wondering about is why do you guys have configuration options using a 12-hour format but then display the scheduled time at the node in a 24-hour military time format? Wouldn't it make more sense to choose one time format and stick with it? If so, then just use a 24-hour time format in the drop down menu and remove the "am" and "pm" radio options. At least this seems the most practical to me.
The way it stands right now, because future decisions cannot be used with the 'Decisions - Newest' block (please see http://drupal.org/node/1240080), I have to stay up until 1am every day to manually enable a previously configured & future decision. This is very annoying and I can't keep this up forever! >:(
Thanks
Mike
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | decisions_date_error01.gif | 4.31 KB | BigMike |
| #1 | decisions_date_error02.gif | 2.18 KB | BigMike |
Comments
Comment #1
BigMike commentedHere are some screen shots. The closing dates in the 2nd image should really say "0:00" and "0:00", which is the 24-hour military time equivalent to 12:00am of a 12-hour time format that has been selected in the 1st image.
Comment #2
BigMike commentedAlso, this is occurring on both my test site and my production site. So I have verified this major loss of functionality bug on two different Drupal installs.
Comment #3
travisjbennett commentedI haven't been able to find this bug yet. It would rock if someone can fix it.
(Follow)
Comment #4
aimutch commentedI've experienced the same issue. The selection of "am" and "pm" is being completely ignored in the start and end dates. It looks like some code was ported over from another module to handle the date selection but that code doesn't support am and pm selection. The fix is probably to have a 24 hour time selection in the drop downs. I'm looking through the code to see if I can figure out how to manage that.