Closed (fixed)
Project:
Clientside Validation
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Jan 2013 at 18:54 UTC
Updated:
16 Sep 2013 at 11:41 UTC
Jump to comment: Most recent file
Comments
Comment #1
liam morlandFix attached.
Comment #2
liam morlandImproved patch works with months expressed as numbers or letters.
Comment #3
attiks commentedThanks for the report and the patch, but I think it will be better if we get a list of months (and a list of abbreviations) from the server (stored in the settings.clientside_validation) so they can get easily translated.
Comment #4
liam morlandUpdated patch.
Comment #5
attiks commentedLooks good, I'll try to run some tests tomorrow and commit this
Comment #6
durum commentedAny progress on this?
Comment #7
attiks commentedCommitted to latest dev version, thanks
Comment #8
kpaxman commentedThe previous patch(es) fail to resolve this issue. Here's a patch against the latest dev that does.
Note that in actual use I have to combine this with the patch from #1902840 so that it works on dates where the selected month is shorter than the current month.
Comment #9
liam morlandThanks @kpaxman.
Comment #10
andyzhang commentedThe validation error message is as the following:
"The value in [field label] is not a valid date.".
I am posting the error message so that the ticket can be searchable by other search engines with the error message.
Comment #11
jelle_sPatch in #8 no longer applies, but it seems to have been fixed already in the latest dev. Can anyone confirm?
Comment #12
jelle_sThis has been fixed in the latest dev.