pca2014

@jdembowski

You’re not understanding the technical nature of this issue, which is why you see this as a hijacking. These problems are all related and I’m trying to work through the issues with anyone who cares to work through the problems with me, because where is the author to help all these people? His responses are almost robotic (AI).

@jdembowski

Everyone is having the same issue with the last update. I’m trying to help people and we are documenting it on each post and comment for this topic. This will help other people. I don’t understand your objection to @mausoftware

@electrowordpress

Rollback to the previous version. I’m running CF7 v5.3.3 and WP 5.7. That will give you time. There seems to be a more bugs in the puzzle.

@mausoftware

Yes, exclude the URLs which have the forms.

@mausoftware

Here is the thread. Maybe you have to make a settings change? Part of the conflict was the deferring of JAvaScript, so that is what they solved, I think. but the second problem is the cache. Their solution was to “Exclude contact form page from caching. Simple!” If page speed is not an issue, do that.

WP-Rocket vs LiteSpeed

akkiverma commented 10 days ago

@scooby75

Sounds like a JS conflict. Try disabling every plugin except CF7 and then test while logged in as admin; that will at least rule out your other plugins.

Someone suggested there might be a conflict between CF7 v5.4 and WP v5.7. I haven’t tested that but I do know that CF7 5.3.3 works with WP v5.7.

What errors are showing up in the “console” tab of “developer’s tools” for Chrome or whatever browser you’re using? That should give us a clue.

• This reply was modified 3 years, 8 months ago by pca2014.

@scooby75

You can test by logging in to your website as a WordPress user. If the problem goes away then it’s likely #1 or #2, since logged in users will automatically bypass the cache and the combining/deferring of JavaScript.

• This reply was modified 3 years, 8 months ago by pca2014.

Everyone on the forum is having this issue. It is caused by the CF7 v5.4 update due to the author’s use of nonces (security tokens) and a common JS library. There are three known reasons this could be happening. The first two are bypassed when logged in as a user because that will bypass your cache and minifiction of JavaScript (combining/deferring).

I think #2 might be your solution. I think it break the animation like it broke all of my animated layersliders.

1. Nonces in CF7 expire after 12 or 24 hours if the form page is cached. You either have to recache every 12 to 24 hours or permanently uncache the page.

2. Minifiction of JavaScript and (combining/deferring) will break the forms. This is sometimes done through a cache plugin but not always.

3. WooCommerce conflicts with CF7 v5.4. There is a workaround for this.

Woocommerce Bug

Like most people I’ve rolled back to v5.3.3 because all of these workarounds will slow your website and hurt your SEO.

• This reply was modified 3 years, 8 months ago by pca2014.

@electrowordpress

seem to have cropped into the problem that the contact forms dont send unless user is logged in.

Everyone on the forum is having this issue. It is caused by the CF7 v5.4 update due to the author’s use of nonces (security tokens) and a common JS library. There are three known reasons this could be happening. The first two are bypassed when logged in as a user because that will bypass your cache and minifiction of JavaScript (combining/deferring).

1. Nonces in CF7 expire after 12 or 24 hours if the form page is cached. You either have to recache every 12 to 24 hours or permanently uncache the page.

2. Minifiction of JavaScript and (combining/deferring) will break the forms. This is sometimes done through a cache plugin but not always.

3. WooCommerce conflicts with CF7 v5.4. There is a workaround for this.

Getting HTTP 403 and HTTP 400 responses when submitting form or refreshing nonce

Like most people I’ve rolled back to v5.3.3 because all of these workarounds will slow your website and hurt your SEO.

@ethical

not for me, i should add the forms work fine if logged in as admin on wordpress, but not for the public

So the problem appears two fold for you. One, the bug in WooCommerce is interfering with the CF7 v5.4 nonce. There appears to be a workaround for WooCommerce on the GITUB page link above.

Second, your cache will cause will cause the CF7 nonce to expire after 24-hours. So you’ll either have to re-cache the for page every 24-hours or permanently uncache the form page.

So far, there appears to be at least three was to kill CF7. The third being the deferment of JavaScript.

No wonder so many people are have issues! Because it’s possible to have all three conflicts layer on top of each other. This explains why some people keep having issues even with the workarounds I found.

@sharbelz

I tried disabling all other plugins, but it is definitely related to WooCommerce. Not sure if it existed in previous versions and went unnoticed.

The problem doesn’t affect the previous version of CF7 v5.3.2 because that version doesn’t use “nonces”. Nonces were added by the CF7 author in v5.4, which is why people with caches are seeing the forms becoming dysfunctional after 24-hours. In your case, instead of an issue with the cache, WooCommerce is interfering with the CF7 nonce.

So it looks like the use of nonces is causing more than on headache for CF7 v5.4 users.

@sharbelz

Might want to take a look at this thread. It appears to be a bug in WooCommerce.

Getting HTTP 403 and HTTP 400 responses when submitting form or refreshing nonce

WooCommerce breaks other plugin’s ability to send POST requests to REST API (rest_cookie_invalid_nonce) #28364

@jbennett45

I cannot still believe they are hanging on. Government clients can be like that too.

IE is pretty much EOL now. I’m guessing CF7 may not work with it going forward. IE only has 2% worldwide marketshare at this point. Does it really matter anymore?

New feature development for the browser was discontinued in 2016 in favor of their new browser Microsoft Edge. Since Internet Explorer is a Windows component and is included in long-term lifecycle versions of Windows such as Windows Server 2019, it will continue to receive security updates until at least 2029. Microsoft announced in August 2020 that as of August 2021, web-based Microsoft 365 products will no longer support Internet Explorer, while Microsoft Teams ended support for IE earlier in November 2020.

• This reply was modified 3 years, 8 months ago by pca2014.

The easiest way to check if you’re being affected by JavaScript (deferment/combining) or caching is to log in as Admin and test the form. Logged in users automatically bypass all caches to include the minification (deferment/combining) of Javascript. If the form works, then somewhere Javascript is being minified (deferment/combining) and/or your pages are being cached. Both problems have to be solved for the form to work.

To be clear, a website doesn’t require a WordPress caching plug-in to be cached. Some themes have caching functions and some hosting plan servers have caches built in too. If you’re using Cloudflare (minification/rocket loader) that could possibly have an affect.

Somewhere Javascript is being minified (deferment/combining) and/or your pages are being cached. Both problems have to be solved for the form to work.

I rolled back to the previous version of CF7 5.3.2 because these fixes have a negative affect on performance.