Viewing 7 replies - 1 through 7 (of 7 total)
  • Please post a URL to your form.

    If it is not required you can leave the field as is: mm/dd/yyyy and submit the form.
    If you delete the mm/dd/yyyy, and submit, it will show that error. But maybe if it is not required, and it is blank, it should ignore that. is that the problem?

    Mike

    Thread Starter jrwmacdonald2

    (@jrwmacdonald2)

    That is how we used to use it – we’d just leave the field with the default mm/dd/yyyy and hit submit – no error. But It no longer allows that (the field is set to not required).

    A URL to your for would be helpful to me to verify problems.

    I am re-coding so if not required, it can be blank, and it can be default mm/dd/yyyy and hit submit – no error.

    This will be fixed in Beta 4 tonight, not sure if any more 3.xx versions will be released.

    Thread Starter jrwmacdonald2

    (@jrwmacdonald2)

    I’d love to give you the URL – unfortunately its not available outside our network. (We use the form to capture reference question statistics at an academic library – it is a fabulous plugin by the way).

    I’m not sure when I’ll be able to move to version 4. Any idea when the problem crept in – perhaps i can roll back to an earlier version until I can move to 4?

    Thanks for your super fast response to this.

    I patched it into the 3.xx version but did not change the version, so this is how to get the new code:
    https://www.fastsecurecontactform.com/update-to-the-latest

    Thread Starter jrwmacdonald2

    (@jrwmacdonald2)

    Wow thanks for the quick response – works! Thanks Again!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Date field now essentially required’ is closed to new replies.