Conflict issue with WooCommerce

Sorry, I tried again and discovered that the form doesn’t work on all devices (desktop to mobile) only if user isn’t logged in.
The conflict only exist if WooCommerce is activated.
The behaviour after submit clic on form is a perpetual loading icon remaining in the same page. Can anyone help me? I’m going crazy!

Ciao Luca,
i’ve the same issue (infinite spinner) but this happens regardless of being logged in or not but only in the product page!

from apache log i got this errors for each mail sent:
AH01067: Failed to read FastCGI header, referer…
(104)Connection reset by peer: AH01075: Error dispatching request to : , referer…

and from the browser side from the js console I got:
/wp-json/contact-form-7/v1/contact-forms/30015/feedback error 503

and a json response like:
`Response?{type: “basic”, url: “https://blitzlift.eu/wp-json/contact-form-7/v1/contact-forms/30015/feedback”, redirected: false, status: 503, ok: false,?…}

at least in my case I think it is related to a php error during submission, anyhow it happens only in my production server (who has modsecurity and nginx) and not in my dev server. In addition actually i’m unable to reproduce the error even with the same wordpress and plugins version ??

UPDATE: after other analysis I discover that the contact form doesn’t work at all if the user isn’t logged in (and WooCommerce active). I solved the issue with a downgrade WCF7 to the previous version. I noticed on Contact Form 7 plug-in reviews that in the last mont many reviews is very weak, so I suppose some bugs in the last update that have to be solved from the developers.
I hope in a new plugin update.

I second this issue, finding same problem on all sites with WooCommerce and CF7…

@lucaminici unfortunately on my side the downgrade (to version 5.2.2) did not help!

and please check the wpcf7 issues on github that may clarify the current situation of the plugin!

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

Found the issue! At least in my case was caused by flamingo who has wp_insert_post() at plugins/flamingo/includes/class-inbound-message.php (283:20) but it needs to use wp_update_post().

The function wp_insert_post will not insert an empty post, and this can cause unexpected problems if you’re passing an ID (as in the flamingo case).

to solve the issue disable flamingo OR replace flamingo/includes/class-inbound-message.php line 283 with
$post_id = wp_update_post( $postarr );

hope it helps!

Thank you Erik, I don’t use Flamingo, but can be a good path to reach the solution for other users.