This thread is resolved. Here is a description of the problem and solution.
Problem:
A Form is included on a page, but the submit button is completely inactive and does not submit the form.
Solution:
In this case the client was including a View inside the form in such a way that there were nested forms, which is not admissible in HTML. The closing /form tag of the nested form was being interpreted as the end of the main form.
This support ticket is created 6 years, 6 months ago. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
If the submit button does not work the most likely explanation is that you have JavaScript errors on the page, which you can check in your browser console.
I can look if I know what page the form is added to.
I visited the page with the form and submitted the form with a test title.
The form appeared to submit, displaying the message specified in your form and as shown in the screenshot, and checking the back-end the corresponding post was created.
In short, everything seems to be working normally.
This is very strange... I can see it worked for you... you managed to submit an application as there is a new post created in the backend.
But I tried with an admin role via google chrome and with a candidate_premium role via firefox and could not submit any application ...
I am bit lost...
Eric
NB : The other thing is your application post was submitted but the email notification to the job post author was not sent.
I'm not sure what to suggest. I ran my test with the user you created (admin) in Chrome.
It worked for me and I didn't see any errors in the browser console.
But if it is not working for you I would expect, perhaps, to see errors in the console, can you check that?
Also keep an eye on the network tab in your browser dev tools. If the submit is happening but nothing is being returned you should at least see the post submission network request.
I don't see any error in the browser console when using my admin login or a candidat_premium login.
I tried with your admin login via chrome and it works indeed... so it's not a browser issue I think.
The only difference with my other tests is you don't have any stored resume to automatically embed in your application... Is there something wrong in the embedded resume ?
Looking at your form I'm not sure what your intention is.
The form includes a hidden parent post selector and a hidden generic email field which has no value but which is set to be saved to the database, and it also includes a View which lists candidature posts of the current author (although why you list these within the form is unclear).
Because you have a hidden parent post selector I assume that this form is intended to create child posts, and you arrive at the form by clicking a child post link from a parent post.
Could you clarify the workflow, and perhaps you can give me credentials for a user that I can use for testing this workflow where I can see the form submission not working?
I'll mark your next reply as private. In the credentials template you can provide the credentials for such a user (skip the FTP part).
The first thing I noticed is that the link from the button to your child form is wrong.
Instead of inserting the link using the child post link shortcode (as described here: https://toolset.com/documentation/user-guides/cred-forms-for-child-content/) you are manually entering the URL into a Divi Button module and appending the URL parameter to set the parent using the wpv-post-id shortcode.
The problem is that the Divi Button module does not evaluate shortcodes, and so the post id shortcode is not resolved and the link is incorrectly formed. (You can verify that by hovering over the button, or inspecting it in your browser dev tools.)
Can you first fix that—by inserting the link using the child post link shortcode inside a text module—and see if that improves things.
If not I will resume testing once you have done that.
I did not delete the button called "postuler" but I added a text module with the link I previously inserted in the button in order to test this solution :
Postuler is now inserted in a text module just below the button.
When clicking on this link I am redirected to the page where I can apply for this job, but the "envoi" button on the application page remains inactive.
What I do not understand is as a 'toolset-helpdesk' user you can click on this button "postuler", get redirected to the application page and then click on "envoi" so that a new application is registered in the system. Problems seem to arise only when we automatically embed a stored resume in the application.
I tried again, and I noticed that the submit button is not within the form itself, as you can hopefully see in the screenshot.
Note that the form tag is closed before the submit button.
I think the issue here is that—I don't know why—you include a View inside your CRED form. A View includes a form (for search filters etc.) and so you are effectively nesting forms.
That is not possible in HTML.
You should remove the View from your form and include it separately on the page. (You can have more than one form on a page, but you cannot have a form appear within a form.)
Well I am a bit confused as all this was done with Shane... I explained I wanted to embed the candidate's resume in the application and he made me do this...
I will check for the submit button but i am really lost on this "embedded resume" and need some help to sort it out.
If I cannot embed the view I would need at least to embed a link to the candidate's resume in the application form.
I also would like to add that this worked a few weeks ago (embedded view).
Please let me know how we can do to have a specific candidate apply for a specific job and embed his stored resume.
Many thanks in advance, maybe we can liaise with Shane who formerly helped on this. Whatever works.
