Messages not showing on submit

@robertshur ::

I’m having a similar issue with my contact form. Once ‘send’ is clicked, the form clears. I do receive the emails, however, the form does not inform the user that the message has been successfully sent.

https://misgood.com/lets-chat/

Thanks for help.
https://www.ads-software.com/plugins/contact-form-7/

@johnmisgood: There is an html error after your country select, a closing div tag which should not be there.

@robertshur: These is an html error after your submit input, one closing div tag too much.

@both: As this closes the main CF7 div, the browser (FF 43.0.4) also sees it as the end of CF7 form, and due to this the CF7 script.js can’t find the relevant div.wpcf7-response-output within its form to output the error/success response and tries to append the message to an empty/not existing $responseOutput object…

It works now. Thank you very much!

Hello guys!

I have similar problem and i partially know the cause.

So my form acts perfectly as long as i don’t add on_sent_ok action hook to “Additional Settings” (I need to track form submission as an event).
I see the green box with the message of successfull submission as well as i receive emails.

But if i add this action hook, i still receive emails but i don’t see a confirmation of it being sent.

This is how the on_sent_ok hook looks like:
on_sent_ok: “_gaq.push([‘_trackEvent’, ‘Запрос online’, ‘Отправить’, ‘russian CF’ ]);”

The form is right at the bottom of this page (it’s in Russian): https://sayagyi-u-ba-khin.net/russia/

Could you please help me?

Thank you.

@ov3rfly thanks so much!

@buzztone: Have sent you this message via your contact.

Would actually consider the current behaviour of scripts.js as a bug.

It does not check if the target div is found and continues to use a non-existing object which might break other scripts on page.

A minimum fix would be a console.log message (if console is present). A more sophisticated fix would use the current form id for response placeholder div or similar.

Very similar problem with this other bug in ajax error handling. There should be some kind of notification (visible or to console) about failing ajax.

As soon as scripts.js is made more bullet-proof, you could add some hints about finding/resolving problems like nested html etc. on your page. Bad html and broken error handling is not a “javascript conflict problem”.