I have embedded a post form on this pageL: hidden link
To reproduce this bug:
1. Fill out fields first name, last name, email, Your group size?, How many days of fishing do you want?, and the First choice date field.
2. Skip all other steps and on the last page of the wizard, click "SUBMIT"
—> The resulting new Form post that's created has all data that was input except the date field is blank.
Hello. Thank you for contacting the Toolset support.
With the form you shared: hidden link
To reproduce this bug:
1. Fill out fields first name, last name, email, Your group size?, How many days of fishing do you want?, and the First choice date field.
2. Skip all other steps and on the last page of the wizard, click "SUBMIT"
==>
I tried to follow the above step and fill the form fields and when I click on "Next" button I can see the following JS on the browser's console and stuck on the same form step. I could not able to move to the next step.
Uncaught TypeError: Cannot read property 'call' of undefined
at $.validator.check (autoptimize_single_388945297ddb72c9050260bc4f202fc8.js:37)
at $.validator.checkForm (autoptimize_single_388945297ddb72c9050260bc4f202fc8.js:25)
at $.validator.form (autoptimize_single_388945297ddb72c9050260bc4f202fc8.js:24)
at n.fn.init.valid ((index):1733)
at HTMLFormElement.onStepChanging ((index):6673)
at HTMLFormElement.dispatch (jquery.js:3)
at HTMLFormElement.r.handle (jquery.js:3)
at Object.trigger (jquery.js:3)
at n.fn.init.triggerHandler (jquery.js:3)
at goToStep ((index):5034)
Just like the another ticket, when the page is loaded: hidden link
- I can see the followng JS error on browser console:
There is no JS error when I use the form , but I disabled the Autoptimize plugin anyway. Here is a video of filling out the form (the console is visible and you can see no JS errors occur): hidden link Also below is the post that was generated when the form was filled out in the video. As you can see, there's no date in the field that a date was selected for.
I had another bug regarding the lag that happens whenever a Toolset form uses the built-in datepicker control. The workaround employed for that has resolved this issue.