Posted by mnapier on June 26, 2009 at 3:34pm
| Project: | Office Hours |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I'm working with the 12hrs time format and attempting to set a closing time as 12:00 am (midnight). When choosing 12 00 AM it NULLS out the day in the database. Anyone else running into this? have a fix?
I'll see if I can come up with a patch in the meantime.
Comments
#1
Just noticed that selecting 12 00 PM gets switched to 12 00 AM on the next edit and then the previously defined bug ends up wiping out that day.
#2
Here's a patch to fix the 12 00 PM from switching to 12 00 AM when editing.
#3
Midnight fix patch. makes it so 0 (midnight) can be stored in the database.
#4
Thanks!
commiting both...
#5
something else must have not jived well with these patches on the latest release, there still seems to be some issues with 12 am.
#6
Original patch was committed here: http://drupal.org/cvs?commit=230630
If you are still having issues, please try to describe them so we can fix them :)
#7
I'm using the latest version available on the module's page, and if I set or change an Until time to 12:00 AM, it wipes the whole Office Hours fieldset.
I just checked, and it also wipes if I set the From time to midnight.
I'm using 12 hour settings, granularity is Hours.
btw, it seems to ignore granularity, since the drop-down menu for the minutes shows all minutes from 00 - 59. Unless I'm misunderstanding what the granularity is meant for.
Unfortunately, I can't use this module with this bug. Our building closes at midnight. I really like it though and will keep an eye out for updates.
#8
#7: Just to be sure, are you using the Drupal 6 dev release or something else?
#9
Sorry I guess I didn't mention the version. Yes, I'm using the Drupal 6 dev release. I was going to apply the patch mentioned above, but I noticed that the code from the patch was already in the version of Office Hours that I was using.
#10
Having the same issue with 6 dev release. In the 12 hour format, if I choose 3pm - 12am, it does not save correctly. Those set of hours will just blank out.
#11
fix committed
#12
Closing issue, since :
#13
Automatically closed -- issue fixed for 2 weeks with no activity.