Forum Replies Created

Viewing 15 replies - 16 through 30 (of 73 total)
  • 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.

    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.

    • This reply was modified 5 years, 4 months ago by pca2014.

    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.

    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 implementthe 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.

    @p_r_i_m_e

    managed to get it working by disabling ajax form submission

    Makes sense. Ajax contains Javascript. It’s either a conflict or somewhere your Javascript was being deferred. Again, being logged in as Admin bypasses that.

    @avniy

    you could also reduce the Cache Lifespan to less than 24 hours (I set it to 3 hours right now) to solve this conflict.

    True but it will have an impact on SEO performance, especially if you’re using CloudFlare or CloudFlare Argo or a similar service that caches your website.

    did you experienced the CF7 issue also on websites that are not under a caching system ?

    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.

    @tobig77 @p_r_i_m_e

    We have the same issue. Contact Form works normally, if the user is logged in.

    This is because logged in users automatically bypass all caches to include the minification (deferment/combining) of Javascript. 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 effect too.

    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 because these fixes have a negative affect on performance.

    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 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.

    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 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.

    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 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.

    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 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.

    @jerffesongd

    Because of the use of “nonces” (security tokens) in FC7 v5.4, you’ll either have to refresh your page cache every 24-hours or uncache the page to keep it working.

    Make sure you check your page 24-hours after the last time it was cached to see if the form is still working.

    This is just a workaround until the problem is fixed.

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

    @ditko74

    You’re on the right path. Deferring JavaScript will break CF7 v5.4 and caching will too. I also had weird issues with minification enabled too. I like a lot of others just rolled back to the previous version until the author provides a fix.

    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 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.

    FYI… CF7 v5.4 uses “nonces” security tokens. If you don’t refresh the cache every 2-4hours or uncache the page, the form will stop working.

Viewing 15 replies - 16 through 30 (of 73 total)