-
Posts
-
Hi,
I need your advice. I have the CF7 plugin in several Enfold installations. Since a few days the submit button does not work anymore. The form hangs with spinning “hourglass”. CF7 recently had an update to version 5.4 and many other users with different themes have the same problem. The developer of CF7 does not get any further. Why am I writing in this forum? When I switch to a default theme, the CF7 plugin works as expected. I can’t get the problem solved with Enfold. It seems to be a combination of WP, theme and plugin.
To try it out, here is a link to an affected contact form: https://dataworx.de/kontakt/CF7’s support forum has a lot of threats on this issue right now. But as I said, with a default theme it works. Only in an “extended” wordpress environment it seems to have problems, among others things with the Enfold Theme.
Thanks for your opinions, hints and tips.
I have forgotten something else:
It works with logged in users. Only with normal website visitors there are these problems. The browser consoles show authentication problems.Hi Mkilgus,
Please send us a temporary WordPress admin login and login URL so that we can have a closer look. You can post the details in the Private Content section of your reply.
Best regards,
RikardHi Rikard,
there are hundreds of user in the support forum of CF7 with same or similar problems. They are running hundreds of different themes. One answer from CF7 is this one:
__________________________________
The Flatsome theme customizes the CF7 form appearance and hides the default loader and shows the theme loader.
CF7 made some changes to their JS which requires Flatsome to made changes to their JS to customize the forms.
So the issue is not with the Contact Form 7, with new updates Flatsome might solve this issue.
__________________________________Is this an issue for Enfold also?
You will receive an admin login for one of the affected sites in the privat sectionThanks in advance
Michaelyou have set the acceptance button – that is absolutely the right way.
Only if the acceptance : “Ich stimme der Datenschutzerklärung zu.” is marked the submit will work ;)Edit : ok it does not send – on page / tab2 of contact form 7 “Mail” have you any error messages? – because cf7 is very sensitive if the recipient address does not correlate with the domain.
Hi Guenni007,
I´ve seen no errors before CF7 update to V5.4.
And the Email address in tab “Mail” is the same domain.Regards
MichaelThe CF7 plug-in breaks my Enfold slider and WP LayerSlider too. Seems like some kind of JS conflict.
@corefocusgroup,
is this behavior reproducible? What happens if you rollback to Version 5.3.2?
@Rikard,
do you still thinking/working on this issue? May it be possible that the update of CF7 V5.4 causes different problems within the Enfold theme because of some JS issues/conflicts?
Thanks in advance
MichaelI have already updated and rolled back several times, maybe a half-dozen times. When I update to CF7 to version 5.4 it breaks my website animations and sliders. When I rollback to CF7 version 5.3.2 everything works fine. I think it’s a JS issue. It seems to affect both the Enfold layerslider and the WP Layerslider. It must be some kind of conflict. My forms still work which is odd when others have reported their forms don’t work. I can only assume a conflict which seems to affect multiple themes and functions.
I am aware of the issues when users update to CF7 5.4. After testing, I today updated from v.5.3.2. to v.5.4 and all 3 forms are sending without any problems. The site is running the latest Enfold version and has Layerslider enabled. The site does not use a caching plugin (Enfold performance enabled: js and css compression) and does not use reCaptcha. Looking at the threads on the CF7 support forum, having reCaptcha enabled and use of third-party caching plugins seem to be relevant to the issues arising.
yes, it´s really surprising that the CF7 update has such different effects (depending on the environment).
@Rikard, your opinion?I´ve just updated the Enfold theme to 4.8. The Contact Form 7 plugin seems to work correctly now.
@rikard please, what changes are responsible for this? Or in other words: What was the problem with Enfold and CF7? Maybe this information can help many other users (not only Enfold user).Thanks and best regards
I updated to Enfold v4.8 with no issues. Then I updated CF7 and it again breaks all of my Enfold Sliders and the WP Layerslider on every page across the entire website with no exceptions.
I’ve discovered the issue in my case. WP-Rocket breaks the website when the option “Combine JavaScript files” is enabled. Considering how many different caching programs and themes there are, this may explain why CF7 is breaking so many different things. Clearly a JS conflict issue.
Offhand does any know which CF7 JS files to exclude from combining?
I spoke too soon. Disabling WP-Rocket the option “Combine JavaScript files” fixed my sliders but the form is now broken. Disabling WP-Rocket entirely fixes the forms but that’s obviously not a solution. CF7 clearly has an issue with being cached. Now I’ll need to figure out how to exclude it from the cache in way that doesn’t kill performance.
RESOLVED?
I believe I’ve now identified the issue. Caching CF7 JavaScript can break the functionality of the form, animations and other things site wide. I’m using Enfold v5.8 and CF7 5.4 and WP-Rocket v3.8.5. – all the latest versions.
In WP-Rocket under FILE OPTIMIZATIONS I had to disable the following options:
1. Combine JavaScript files
2. Load JavaScript deferredI assume similar settings in other caching programs will resolve the issue.
I can exclude CF7 files from being combined or deferred but I don’t know which files those are. Could anyone tell me what CF7 JavaSCript files to exclude?
NOTE: In a CF7 forum I read about the forms breaking after so many hours due to “nonce” issues. I will have to followup on that.
According to this post by the Autoptimize author, you need to add
wp-includes/js/distand possiblywp-includes/jsto the excluded js list.Then, suggested in this post, you can exclude the following:
/jquery-?[0-9.]*(.min|.slim|.slim.min)?\.js /wp-includes/js/dist/vendor/wp-polyfill.min.js /wp-includes/js/dist/vendor/lodash.min.js /wp-includes/js/dist/api-fetch.min.js /wp-includes/js/dist/url.min.jsAccording to this post by the Autoptimize author, you need to add wp-includes/js/dist and possibly wp-includes/js to the excluded js list.
Are those files specific to CF7? They look like general JavaScript files.
Hi Mkilgus,
I’m very sorry for the late reply. If updating to Enfold 4.8 worked for you, then I can only assume that Enfold was at least partly responsible for the problems you were having, since we had some problems with the new jQuery version in WordPress core. Those problems are now solved in 4.8.
Best regards,
RikardHi corefocusgroup,
Thanks for sharing your findings. I’m not sure which files to exclude unfortunately, did you the files listed by @barnez1?
Best regards,
Rikardit was not the theme update itself that solved the problem for a short time. I assume, that the cached pages refreshed after theme update. The problem with CF7 forms reoccurs every 12 (or 24?) hours. It has to do with nonces and caching life time.
wp-rocket is writing:
“Nonces are security tokens in WordPress. They get printed into the HTML source code.
Nonces can only be used once (hence “n once”), and they are only valid for a certain length of time: 12 hours by default, but developers can change that value. On a cached page, the nonce can expire in the background while its ID is still present in the HTML source code of the page. If that happens, the HTML source is referencing an invalid nonce and things break. This can affect all kinds of functionality, from form validation to the visual appearance of a post grid, and a lot more. In some rare cases it could even lead to a completely blank page on the front-end.”If I exclude the pages with CF7 forms from beeing cached, all works fine (longer than 12 or 24 hours).
I’ve been on the WordPress CF7 support page talking about all of this for a week. The developer made significant changes that broke the form for almost everyone. Caching javascript and nonces are causing forms to fail. I think almost 100% of the users were impacted.
- You must be logged in to reply to this topic.