Closed (fixed)
Project:
Event
Version:
5.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Mar 2007 at 21:08 UTC
Updated:
19 Jul 2007 at 14:52 UTC
In both the "Start date" and "End date" input areas, there are problems with the month and minute droplists:
Month:
Whenever the edit-node page/form is opened, both values reset to "January". While it makes some sense, given the fact that it is at the top of the list, I'm pretty sure it's a bug because all of the other fields default to the current date and time when creating a new event.
Minute:
Whenever the edit-node page/form is opened, any value of less that 10 is reset to 00. While I'm not entirely sure if this is a bug or not, it seems kind of arbitrary and not particularly useful.
Any help on either of those would be much appreciated. Thanks.
Comments
Comment #1
grisu commentedHi,
Just upgraded to Drupal 5.1. I get the same mistake.
In addition.. when creating an event, the default value of the 'month' is always January.
regards,
Alexander
MySQL-DB 4.1.11
PHP 4.3.10-16
Webserver Apache/1.3.33
Comment #2
grisu commentedSolved for now. Was it the latest event.module or the new daylight saving time?
Comment #3
(not verified) commentedComment #4
Walt Esquivel commentedUnless this is a duplicate of some other posted issue for the events module, the "month" bug is not fixed and still remains. I don't know about the "minute" droplist cited in the original post at the top of this page since I haven't had need to change it from the "00" default.
To duplicate, simply go to any group on g.d.o. and create an event with any month other than January. After you've created the event, click to edit it and you'll see the month defaults to January. So, this is still a valid bug.
So why was this marked as "fixed" by grisu on 3/12 and then "closed" by anonymous on 3/26? Could it be that g.d.o is not using the latest events module?
Thanks,
Walt
Comment #5
Walt Esquivel commentedPlease see my comment above at #4 and also over on g.d.o as to why I'm changing the status from "closed" to "active".
Thanks,
Walt
Comment #6
Walt Esquivel commentedOK, this issue appears to be specific to g.d.o per http://drupal.org/node/159735.
Thanks,
Walt