I also saw the same when using LightSpeed cache.
It is also more sensitive to failures in FireFox.
-
This reply was modified 2 years, 6 months ago by
mikewill34.
Hi @mikewill34
I hope you’re well today!
As for JS minification
If you are using WP Optimize plugin, try this:
– go to “WP-Optimize -> Minify -> Advanced” page and you shoudl see “Minify Cache Information” section there
– click on the “Show information” link next to “wpo-minify-footer…min.js” file and it should show list of JS files with “Exclude” option next to each.
– check the same for “wpo-minify-footer….min.js” file
You would want to exclude “/wp-includes/js/jquery/jquery.min.js” from it usually and also all the files that have “/plugins/forminator/” part in the path.
The reason I’m not stating specific Forminator files is simple – I have no way of knowing which specific ones are related to the issue on your site. It isn’t always the same and often depends also on how theme and other plugins work and “interact” with other scripts and CSS on site. If such a “global” exclusion solves the issue and you’d still like to try to keep at least some of those files additionally minified (though note that most of them are already minified anyway out of the box) then you would need to try to gradually re-add them.
But I would just keep all the JS files in /plugins/forminator page excluded.
As for cache
This isn’t unusual and unexpected. Caching can affect any type of dynamically generated content/dynamic features (such as e.g. forms).
I would suggest starting with two things:
– first, make sure that on form’s “Behavior” settings page the “Load form using AJAX” option is enabled
– and if that’s not sufficient, try also enable “Prevent page caching on form pages” option
Kind regards,
Adam
Thanks for the VERY useful information.
I looked at the cache logs and found that most of the javascript files already had “min” in their file names, so are most likely are already minified.
Therefore simply disabling JS minification was enough to get the form working again. Armed with this knowledge I was able to switch back to LiteSpeed for caching (as our hosting has it embedded in)
Hi @mikewill34,
We are glad to hear that the issue has been resolved and marking this thread accordingly. Please let us know in case you need further help.
Kind regards,
Zafer