I take it that the form is set to submit via ajax, which would account for why JS errors on the page prevent it from submitting.
It's not clear from the screenshot the source of the errors, but they don't appear to be from Toolset.
So the first step would be to test this page in a minimal install, i.e. after disabling non-Toolset plugins, to confirm that it ordinarily works. Then re-activate plugins to try and identify the source of any conflict that produces the errors.
If you let us know what you find we can try to reproduce the problem.
Then, in the meantime, you can switch to submitting the form via page refresh as a temporary workaround.
I do not have any idea based on the recording your shared and I do not see any concrete information that should cause the issue from the console log you shared.
Can you please share problem URL where you added the form as well as admin access details and let me step in and check whats going wrong with your setup.
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I have set the next reply to private which means only you and I have access to it.
Minesh is on vacation, so I'll be following up on this ticket.
I haven't seen a request for a CSS & JS file like this before, so it most likely has something to do with the custom code snippets used on the website.
If the issue is only happening with Toolset plugins active, have you tried, temporarily disabling the custom code snippets added through the Toolset?
You can disable the code snippet support by adding the following line to your wp-config.php:
define( 'TOOLSET_DISABLE_CODE_SNIPPETS', true );
In case the issue still persists, I'll need your permission to download a clone/snapshot of the website. This will help in investigating this matter on a different server, without affecting the actual production website.
Now out of all above fields that you hide using CSS style="display:none;" - the field "Candidate Name" is required field.
If all above fields are not required in your form - I suggest you should just delete those fields from your form and save the form and then it should work.
Thank you for solving part 1 of the issue. But the main issue is still there.
I mentioned that in the second scenario where form is submitted is user is not directed to the next page.
All backend processing happens just fine but the page does not follow the guidance for redirection on toolset form.
You can test this at hidden link
This is happening for most forms and I am still getting the following error in console -
GET hidden link net::ERR_NAME_NOT_RESOLVED hidden link
GET hidden link net::ERR_NAME_NOT_RESOLVED
New threads created by Minesh and linked to this one are listed below:
My friend,
I did not remove the fields for a reason. I need these fields to show data in email notification. I can't add them to email notification if I don't add them in the form.
I am updating these fields in the backend with cred_save_data before cred_notification trigger hits. This was I am able to email multiple people at once.
The other issue was reported in the ticket and is even bigger because the users are not able to move ahead and use the product. Feel free to create a separate ticket if that is more convenient for you.