Ticket #1617 (assigned defect)

Opened 1 year ago

Last modified 1 year ago

Calendar time data did not match

Reported by: anonymous Assigned to: ant_39 (accepted)
Priority: highest Component: CalendarPlugin
Severity: blocker Keywords:
Cc: Trac Release: 0.10

Description

I get this error when trying to add an event in the calendar. The time date that was entered as: 07/07/10. I also tried: 2007/07/10 ====================== Traceback (most recent call last):

File "D:\Python24\Lib\site-packages\trac\web\main.py", line 406, in dispatch_request

dispatcher.dispatch(req)

File "D:\Python24\Lib\site-packages\trac\web\main.py", line 237, in dispatch

resp = chosen_handler.process_request(req)

File "build\bdist.win32\egg\azcalendar\azcalendar.py", line 305, in process_request File "build\bdist.win32\egg\azcalendar\azcalendar.py", line 46, in process_add File "D:\Python24\Lib\_strptime.py", line 293, in strptime

raise ValueError?("time data did not match format: data=%s fmt=%s" %

ValueError?: time data did not match format: data=07/07/10 fmt=%Y/%m/%d %H:%M

Attachments

Change History

06/07/07 08:53:40 changed by anonymous

I also had the same error, and used the default dates.

Plesae fix.. this is a great and very useful plugin!

06/07/07 09:00:46 changed by ant_39

  • status changed from new to assigned.

You have to enter dates in full format, including HH:MM component. E.g. "2007/03/28 15:30". This is certainly a bug, because the client-side should check that you provided meaningful values, and server side shouldn't fail if nonsense is entered, but it's easy to work around. I'm accepting the ticket, but I won't have time to work on my plugin for at least a month now. Sorry.

06/07/07 11:11:55 changed by anonymous

Ok cool. Could you possibly quickly make it at least default to a particular time like 09:00 (9AM) start and 18:00 (6PM) so that, if we forget to change it, it won't crash.

Other suggestions as I play with it are:
1. Control to set # of months to display
2. Ability to have 24HRS or set time range (like for a work day, 8AM - 6PM)
3. When clicking on the item in the timeline view... it brings you back to the editor.. possibly have a admin/user view of it.
4. In the editor - possibly have a text box area for comments about the item, so that when someone clicks on it as a (user, non admin) there's more info about the item.
5. Mabye custom Event priority fields - for catorizing - similar to project management software.

Thanks!

07/22/07 13:18:25 changed by ant_39

Fixed the original problem in r2508. It now allows omitting the time component. If the time component is missing from begin time, the time component defaults to 0:00. If it's missing from end time, it defaults to 0:00 the next day. I'm leaving this report open to keep an eye on your other topics.

Add/Change #1617 (Calendar time data did not match)




Change Properties
Action