Adding a milestone on the demo results in python error messages

[richard.rowell@…]

Just go to the live demo and try to add a milestone

TracGuide — The Trac User and Administration Guide Python Traceback

Traceback (most recent call last):

File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 406, in dispatch_request

dispatcher.dispatch(req)

File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 237, in dispatch

resp = chosen_handler.process_request(req)

File "/usr/lib/python2.4/site-packages/TracWebAdmin-0.1.2dev_r4429-py2.4.egg/webadmin/web_ui.py", line 109, in process_request

path_info)

File "/usr/lib/python2.4/site-packages/TracWebAdmin-0.1.2dev_r4429-py2.4.egg/webadmin/ticket.py", line 163, in process_admin_request

mil.due = util.parse_date(req.args.get('duedate'))

File "/usr/lib/python2.4/site-packages/trac/util/datefmt.py", line 114, in parse_date

raise ValueError, '%s is not a known date format.' % text

ValueError: 10/22/2007 is not a known date format.

[Emmanuel Blot]

Look at the Format hint right against the date field:

Format: MM/DD/YY

not

Format: MM/DD/YYYY

[richard.rowell@…]

Did you try the date I tried? Seems pretty clear from the error message that it choked on the date.

[anonymous]

Never mind, I did specify a 4 digit date. Though in principal I don't that a python error anytime gives the incorrect date format is a very user friendly way of handling form input.

[Emmanuel Blot]

Replying to richard.rowell@gmail.com:

Did you try the date I tried? Seems pretty clear from the error message that it choked on the date.

Yes and it failed as expected, since you did not use a valid format for the date - that's the point I was trying to explain in my previous comment.

[anonymous]

Sorry to reopen this, but I am wondering if it is the same problem as #6443?

[osimons]

Replying to anonymous:

Sorry to reopen this, but I am wondering if it is the same problem as #6443?

Yes. #6443 closed as duplicate of this ticket.

(PS! No need to reopen the ticket to leave a note.)