Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=13861

Maxdate validation should now work up to year 2099. Not guaranteed to work for date formats containing two digit years ;).

I just tested it and now it accepts my dates properly! Should be good for a few more years now! ;p

Thanks for the quick response!

@mfaber : we can not ask historical date here. It's really just to undersant: why not accept date after 2038 why not accept date after 2099 or before 1901 ?

I first understand the date betwwen 1901 and 2038 for historical purpose, here i don't track if we use DATETIME for mysql.
But i think we use PHP 5.3 and we can have date in 64b
http://en.wikipedia.org/wiki/Year_2038_problem#Solutions

Denis: I initially limited the range to 1900-2038 because it just did not work with dates beyond that (32bit problem)?. Can't remember which component made the trouble. Probably the date picker or the phpjs functions. I was quite surprised yesterday to find min/maxdate working with dates > 2038.

Kept the dropbox style date question at 2038 because the year dropbox would just get too full.
Otherwise I'd be okay with setting limits from 1700-2200 or something else if you think it's useful. Just need to be prepared for crazy things to happen :).

Denis: regarding mysql: reponses to date/time question are saved as a string...so there should be no problem from the DB side.

Hi,

No , leave it for 2.1 :) or just an $config

2.05+ Build 140212 released