It seems that this problem is widespread.
I can understand the frustration of the developer, but this much-loved plugin & very popular plugin is a crucial part of the sites it is installed. It had its share of bugs in the past so I would expect from the developer more attention when releasing updates.
Unfortunately, there is not an easy way to roll back to the previous version of the plugin.
The conflict caused by CF7 v5.4 is two fold.
One, if your caching plugin is deferring 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. If you’re not using a caching plugin there are other plugins or hosting systems that may implement the deferring JavaScript.
/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 page cache every 24-hours or uncache the page.
I don’t consider this a solution, just a workaround due to the performance implications. Both fixes will degrade performance and hurt SEO.
Thank you guys for your comments.
I did a rollback and it looks like all forms are working correctly. I have to mention that the whole procedure was very easy, thanks to WP.
But this is not a solution, as @pca2014 saying it’s a workaround to have the site working properly. I hope the developer will come out with a solution soon.
