DateTime Field Restricted Dates not working

  • collegeplus
    Asked on October 29, 2015 at 4:16 PM

    Hi, I have a form with asks for a date to be chosen. I have restricted the dates to be tomorrow or later only; that is, users can only pick a date which is LATER than today, and today cannot be chosen either.

    I noticed that some responses were coming in with the date selected being the same as the date of the submission, and thought it might have been a time-zone issue or something I couldn't replicate, but I just had a submission come in with a date in the PAST, and looked into things a bit more.

    It appears that if you enter the numbers in each of the 3 fields manually, without using the calendar pop-up, you can select any date whatsoever, even those restricted by the field's preferences.

    For example, if I use the calendar, I can only select tomorrow or later. All other dates have no effect when I click on them. However, if I were to enter 3 in the month field, 20 in the day field, then 2010 in the year field, it would not error out, and allow me to continue the form as normal.

     

    Help!

  • jonathan
    Replied on October 29, 2015 at 7:46 PM

    Thank you for providing more details.

    I checked and test this on your jotform http://www.jotformpro.com/form/52256212718957 but I could not reproduce the issue.

    Check the image below when I did the test.

    DateTime Field Restricted Dates not working Image 1 Screenshot 20

     

    Manually typing invalid dates still gets validated by the restricted date function on the DateTime field.

    Can you please retry again this time and check if issue still persist.

    If you can share to us image that shows the issue it will also help us check better where the issue could be.

     

  • collegeplus
    Replied on October 30, 2015 at 1:36 PM

    The issue is no longer occurring, but I had 2 submissions with dates in the past. What could have caused that?

  • Jeanette JotForm Support
    Replied on October 30, 2015 at 5:57 PM

    The problem could have occurred due to a glitch caused by the recent DB maintenance. Please let us know should you need further assistance.