pca2014
Forum Replies Created
-
Forum: Plugins
In reply to: [Contact Form 7] Since contact form 7 v5.4 – Nonces?Yes, the nonces expire after 24-hours. You have to re-cache the page every 24-hours to reset the nonce. The other option is to uncache the page. Everyone is having these issues. Make sure you’re not logged into your website when you check the form functionality, as Admin your bypassing the cache and the forms will appear to work but they will be broken for public users.
Forum: Plugins
In reply to: [Contact Form 7] cf 7 doesn’t work even after rollbackMake sure you checked the form after 24-hours. CF7 v5.4 uses “nonces” (security tokens that expire after 24-hours. If your website is cached the forms will stop working unless you re-cache the page daily.
Also make sure the form works when you’re not logged into your website. When you’re logged in your bypassing the cache and the form will work anyway, but not for public users.
Forum: Plugins
In reply to: [Contact Form 7] CF7/WProcket form bugThis issue is not related to WP Rocket. When WP Rocket is deactivated and uninstalled, but WP_CACHE constant is set to true in wp-config.php: define( ‘WP_CACHE’, true ); the contact form doesn’t work.
You’re 100% correct. It isn not about WP-Rocket. I use WP-Rocket. I was simply explaining that WP-Rocket had a fix for this CF7 5.4 update problem, which affects any caching plugin that defers JAvaScript. Even if you correct this problem, you’ll still have to clear your cache every 24-hours because of the security “nonces”.
Forum: Plugins
In reply to: [Contact Form 7] Not sending message, only pending…The best option is to roll back. I’m glad someone was able to help that with you. We’re all having to do the same thing.
Forum: Plugins
In reply to: [Contact Form 7] Not sending message, only pending…It’s best to rollback unless you want to take the SEO performance hit with Google. That’s what we did. If the developer does not resolve the issue, then our business will look elsewhere.
Forum: Plugins
In reply to: [Contact Form 7] Not sending message, only pending…I believe the nonce is generated for each form page and expires after 24-hours. When you load the page look at the URL and you’ll see a nonce string after the page URL.
Forum: Plugins
In reply to: [Contact Form 7] CF7 working only one pageDid you upgrade to CF7 5.4? Try clearing your cache and see if it works. If it does then I may know what the problem is.
Forum: Plugins
In reply to: [Contact Form 7] Not sending message, only pending…Sorry, note this is a result of the CF7 5.4 update.
Forum: Plugins
In reply to: [Contact Form 7] Not sending message, only pending…The problem is manifested by a CF7 conflict with caching. I also had thought the form was working in one browser but not another, but that turned out to be false. If you are logged in as Admin in WP then you’re bypassing the cache and the form will work.
The conflict caused by CF7 v5.4 is two fold.
One, if your caching plugin is derring JavaScript then it breaks CF7. If you have WP-Rocket they have issued a fix for the conflict. The WP-Rocket fix can be replicated in other caching plugins by excluding the deferral of this JavaScript script.
/wp-includes/js/dist/(.*).js
But even with this fix in WP-Rocket or another caching program, CF7 forms will fail after 24 hours due to the author’s use of nonces (security tokens). The only way to workaround the problem is to refresh your cache every 24-hours.
I don’t consider this a solution, just a workaround due to the performance implications. Both fixes will degrade performance and hurt SEO.
- This reply was modified 5 years, 5 months ago by pca2014.
Forum: Plugins
In reply to: [Contact Form 7] Contact Form 7 is not sendingThe problem is difficult to diagnosis because one half of the problem is to stop the deferring of the JavaScript file that CF7 is now dependent and the other half is the nonces which have to be refreshed every 24-hours to keep the form working. This is what’s tripping people up.
The CF7 conflict can cause the form to stop working or to just stall. It can also cause conflicts with other plugins dependent on JavaScript, if you opt to combine JavaScript files that are minified in your cache plugin. In my case, my WP LayerSliders stopped working with CF7 enabled.
The problem with the author’s changes is that the workaround is going to have a noticeable performance impact on a website, because we want to defer JavaScript and re-cache pages only when the content of the page has changed to increase our Google PageSpeed score for SEO.
The bottomline is that the new CF7 design will make your whole website slower. There is no reason it has to be this way.
Forum: Plugins
In reply to: [Contact Form 7] Contact Form 7 is not sendingthe conflict caused by CF7 v5.4 is two fold.
If you have WP-Rocket they have issued a fix for the conflict. The WP-Rocket fix can be replicated in other caching plugins by excluding the deferral of this JavaScript script.
/wp-includes/js/dist/(.*).js
But even with this fix in WP-Rocket or another caching program CF7 forms will fail after 24 hours due to the author’s use of nonces (security tokens). The only way to workaround the problem is to refresh your cache every 24-hours.
I don’t consider this a solution, just a workaround due to the performance implications.
Forum: Plugins
In reply to: [Contact Form 7] CF7/WProcket form bugThe WP-Rocket has fixed the issue. The WP-Rocket fix can be replicated in other caching plugins by excluding the deferral of this JavaScript script.
/wp-includes/js/dist/(.*).js
But even with this fix in WP-Rocket or another caching program CF7 forms will fail after 24 hours due to the author’s use of nonces (security tokens). The only way to workaround the problem is to refresh your cache every 24-hours.
I don’t consider this a solution, just a workaround due to the performance implications.
Forum: Plugins
In reply to: [Contact Form 7] CF7 v5.4 Now Works with WP Rocket v3.8.6The WP-Rocket fix can be replicated in other caching plugins by excluding the deferral of this JavaScript script.
/wp-includes/js/dist/(.*).js
But even with this fix in WP-Rocket or another caching program CF7 forms will fail after 24 hours due to the author’s use of nonces (security tokens). The only way to workaround the problem is to refresh your cache every 24-hours.
I don’t consider this a solution, just a workaround due to the performance implications.
Forum: Plugins
In reply to: [Contact Form 7] After update to 5.4.1 send not working – console errorsCF7 stops after 24-hours because the “nonce” (security token) becomes invalid. The only solution is to refresh the cache every 24-hours. I did read in one post that it’s possible to change the lifespan of the nonce but I’m not sure what the broader security implications would be for general site security.
Either way I don’t see this as a long term solution, since refresh the cache every 24-hours can cause a serious performance hit, especially if your using Cloudflare or a similar service and modifying the nonce life may result in security implications beyond CF7.
The plugin should have been designed not to conflict with the cache and the use of nonces should be optional.
Forum: Plugins
In reply to: [Contact Form 7] All my forms stopped workingCF7 version 5.4. has a conflict with caching combining JavaScript and deferring Javascript. If you have WP-Rocket they have a fix. But that’s only half the problem. CF7 now uses nonces (security token) and it has to be refresh every 12 or 24 hours, which means you’ll have to clear your cache once or twice a day.
Look down the forum and you’ll see tons of comments about this.
Be forewarned that if you’re logged in as admin it will may work because you’re likely bypassing the cache. You either need to be logged out of WordPress or access it through a web browser in private mode to test if it’s working for public users.