Date field badly encoded produces error 500

Hi,

I had twice the problem last days. The people encoding the new website we are launching made mistake during the date entry.

Instead of using the calendar or entering the date as "2009-10-01" they entered "1 october 2009" then they saved the item and now I had to go manually in the DB to correct this because there was no way to re-edit the item we had an error 500 because of the bad date format. Both in front and back-end.

Is there a way to validate the date before saving? That would be useful because the server is validating it before the output but that is too late!.

My version is J 2.5.7 FC 2.0 RC9 r1514

1 October 2009 , should be parsed and store properly

but an invalid date e.g
1 octber 2009
ddddaaadd

will cause the 500 error

i am fixing this, there will not be error 500 even if an invalid value is loaded from the DB,

also we can add js validation to force user enter date in the preconfigured format

An exception is thrown when we attempt to display a date that is invalid:

i have added check for this in r1520, also when item form is loaded a warning will appear that a value of the particular date field was ignored (if you want it now):

flexicontent.googlecode.com/svn-history/r1520/trunk/com_flexicontent_v2.x/plugins/date/date.php

flexicontent.googlecode.com/svn-history/r1520/trunk/com_flexicontent_v2.x/plugins/date/date.xml

flexicontent.googlecode.com/svn- ... s_date.ini

Thank you GGPPDK,

I just tested and now no more error 500. Perfect.

There was no mistyping but in fact the back-end is in english and the encoding is in french or dutch.

So "10 avril 2002" is not understand as "2002-04-10".