HubieDoobieDoo

OK, sorry you couldn’t/wouldn’t address the issue.
I am moving to another form plugin.

Thanks anyway for the free use of this free plugin for several years, it was fine while it worked !

I share the concern.
In my case, the conflict is with the theme we use (ThePlaceChild). Seems clear to me that the recent update to ContactForm has made it prone to break, in association with various themes or plugins.
The common point seems to be that it hits an unexpected situation (a null pointer) and doesn’t handle it well.

It may or may not be the fault of the “others” (plugins or themes), but there seems to be multiple such 3rd parties, so it’d be a good idea for ContactForm to not be so sensitive and handle it gracefully.

In the meantime, as ContactForm does not show any sign of willingness to address, and since obviously my Theme has higher priority, I think I’ll migrate to another contact form plugin, sorry.

Please do let me know if I can help problem determination in any way.

From other recent problem reports here, it appears the latest update to Contact Form has made it fragile to what may or may not be “oddities” or “improper/unexpected behaviors” in various themes or plugins (in my case the “The Place Child” theme).

If there are common issues that can be identified, you may be able to render CF more solid and avoid the pitfalls. Or you can decide it’s not your problem.

If this incompatibility will not be addressed semi-promptly, as I cannot move to another theme, I would have to select a CF plugin substitute (curently have just removed the contact form altogether, as a stopgap temporary measure).

Please do communicate on your intentions.

OK, I made multiple tests, and confirm the conflict occurs only when the theme “The Place Child” is activated (my plugins don’t make a difference).

https://themesinfo.com/wordpress-website-template-theplace_child-o8x

Darn. What now?

The above error log was from Firefox javascript console.
Similar error reported under Chrome (appears when clicking the “submit” button on the contact form) :

index.js?ver=5.7.5.1:1 TypeError: Cannot set properties of null (setting ‘innerText’)
at d (index.js?ver=5.7.5.1:1:7423)
at index.js?ver=5.7.5.1:1:7171
at index.js?ver=5.7.5.1:1:894
at index.js?ver=5.7.5.1:1:8223
at index.js?ver=5.7.5.1:1:894
at n (index.js?ver=5.7.5.1:1:1708)
at l (index.js?ver=5.7.5.1:1:6278)
at index.js?ver=5.7.5.1:1:429
(anonymous) @ index.js?ver=5.7.5.1:1
Promise.then (async)
catch @ recaptcha__fr.js:278
o @ index.js?ver=5.7.5.1:1
wpcf7.submit @ index.js?ver=5.7.5.1:1
(anonymous) @ index.js?ver=5.7.5.1:1

• This reply was modified 1 year, 7 months ago by HubieDoobieDoo.
• This reply was modified 1 year, 7 months ago by HubieDoobieDoo.

I just tried disabling all plugins (except Contact Form 7, of course) very temporarily to see if it changed anything. It apparently didn’t.

Theme :
The Place Child Version : 0.1 (based on The Place Version : 1.9.3)

Plugins :
Classic Editor Version 1.6.3
Contact Form 7 Version 5.7.5.1
Display PHP Version Version 1.7
Google XML Sitemaps Version 4.1.8
qTranslate-X Version 3.4.6.8
Slimstat Analytics Version 5.0.3
Sucuri Security Version 1.8.37
UpdraftPlus Version 1.23.3

(sorry, bad form to ride on somebody else’s report — opened my own thread now, apologies for the disruption)

Not sure if it’s relevant or helps in anyway, but the javascript console shows :

TypeError: e.wpcf7.parent.querySelector(…) is null

    d https://www.laplacestmartin.fr/wordpress/wp-content/plugins/contact-form-7/includes/js/index.js?ver=5.7.5.1:1

    <anonymous> https://www.laplacestmartin.fr/wordpress/wp-content/plugins/contact-form-7/includes/js/index.js?ver=5.7.5.1:1

    n https://www.laplacestmartin.fr/wordpress/wp-content/plugins/contact-form-7/includes/js/index.js?ver=5.7.5.1:1

    <anonymous> https://www.laplacestmartin.fr/wordpress/wp-content/plugins/contact-form-7/includes/js/index.js?ver=5.7.5.1:1

    n https://www.laplacestmartin.fr/wordpress/wp-content/plugins/contact-form-7/includes/js/index.js?ver=5.7.5.1:1

    n https://www.laplacestmartin.fr/wordpress/wp-content/plugins/contact-form-7/includes/js/index.js?ver=5.7.5.1:1

    l https://www.laplacestmartin.fr/wordpress/wp-content/plugins/contact-form-7/includes/js/index.js?ver=5.7.5.1:1

    o https://www.laplacestmartin.fr/wordpress/wp-content/plugins/contact-form-7/modules/recaptcha/index.js?ver=5.7.5.1:1
index.js:1:458

    o https://www.laplacestmartin.fr/wordpress/wp-content/plugins/contact-form-7/modules/recaptcha/index.js?ver=5.7.5.1:1

Metoo, but maybe not quite the same issue : the user sees absolutely no effect when clicking the “send” button (no confirmation message, nothing), and obviously no mail is sent.

Just upgraded to WP 6.2 (but the issue predates that by at least a few days)
Server running PHP version: 7.4.33.

Hello, and thanks for the reply, which prompted me to do some more testing… and APOLOGIES, I have now resolved my problem, which lay solely on my side.

It turns out that at some point in my testing, I had set:
$mailer->SMTPDebug = 2; // for verbose output

This generates non-enqueued html output from within the action (at $mailer->send() time), which obvioously triggers the issue with Forminator reporting that there “was some problem during processing”.

Resetting SMTPDebug to 0 (for mute) makes everything work fine again. I don’t know how in my multiple trials I messed up to the point that I copied here test code which obviously was NOT what I was testing.

Very sorry for the false alarm and the wasted time for you.
And thanks again for your great support and patience.

<crawls into a corner, trying to hide in shame>

• This reply was modified 3 years, 7 months ago by HubieDoobieDoo.

Yes, I confirm this gets rid of the error message in the console.

This field being a zip code (in France), they are numbered as 5-digit numbers, first 2 digits being an area code with leading 0, hence the natural way of expressing the limits as (01)000 through (99)999.

No big deal, thanks.

• This reply was modified 3 years, 7 months ago by HubieDoobieDoo.
• This reply was modified 3 years, 7 months ago by HubieDoobieDoo.

(2.07 seems to work fine now. Thanks.)

I guessed that much. Well, it may be helping for that, but… ??

Yes, of course, when the test custom plugin is deactivated, the “thank you” message displays fine.

It also displays just fine when the plugin is activated but its line $mailer->send() is commented out (of course, in that case no mail is sent, he).

When the plugin (with its sending line) is activated, the mail is sent. In my real plugin, I have error catching on the send(), as well as traceing statements thereafter. No send() error is reported, the traceing logs trace in my logfile, then the return; executes, Forminator regains control, and… reports “something went wrong”… I would really like to know *what* and if I can fix it.

It’s particularly frustrating, since everything processes just fine, the mail is being sent and received, it’s just this spurious error message from Forminator (which may be the tip of an iceberg of yet to be uncovered issues and general fragility of my setup).

I had initially considered using the standard DB and PDF integrations and decided against it, for reasons I’m afraid I can’t remember at the moment.
I have some resonably complex business logic for, depending on form input and database interactions, sending bills, fiscal receipts, membership cards, etc…
I might reconsider this alternative if it turns out I’m having too many problems with my custom plugin, but its completely coded by now, and just this one pesky issue baffles me… :-/