Bug #22974 Invalid dates cause problems on the server but aren't reported to user
Submitted: 4 Oct 2006 7:38 Modified: 9 Jul 2013 8:28
Reporter: Andrew Chapman Email Updates:
Status: Closed Impact on me:
None 
Category:Eventum Severity:S2 (Serious)
Version:1.7.1 OS:Windows (Windows XP SP2)
Assigned to: CPU Architecture:Any

[4 Oct 2006 7:38] Andrew Chapman
Description:
Problems occur if you enter stupid dates 2006-02-31 for example into expected resolution date or pre_scheduled_date (those are the DB field names, not sure where they come up in the interface).

It looks to the user like their changes saved, but underneath the update/insert fails. 

I am not 100% certain (we had a non-Eventum releated problem in the same time window), but the users reported that this caused fairly wierd behaviour in the user interface (issues can't be opened anymore and low level error messages appear in the Eventum interface).

How to repeat:
Enter a duff date in expected resolution date and update the issue.

Suggested fix:
Either
1. A bit of JavaScript to check the dates are valid (easy but clunky)
2. Code to catch the insert/update failure and return to the page so the user can correct the date
3. Validation of the post parameters before they go to MySQL
3. Some sort of pop-up date entry control

1 seems the most sensible option.
[22 Oct 2006 11:49] Valeriy Kravchuk
Thank you for a problem report. Please, try to repeat with a newer version of Eventum, 1.7.1, and inform about the results.
[26 Oct 2006 15:54] Andrew Chapman
Double checked and I was actually using 1.7.1 - but it was upgraded from 1.7.0 and the entry in config.inc.php hadn't been changed.
[23 Nov 2006 3:00] Bryan Alsdorf
Hi,

thanks for the report. I have confirmed this issue. I have not seen the strange behavior in the Eventum UI, but can confirm that inserting an invalid date fails. 

/bryan
[9 Jul 2013 8:28] Yngve Svendsen
Hi. Eventum is now a project independent of MySQL, and its new home (including bug tracking) is here: https://launchpad.net/eventum

I am closing this, and ask that the issue, if still relevant, be reported to the Launchpad bug tracker.