Hi @colouritin ,
I’ve tried to replicate this error but it seems to be working fine on my test lab where I don’t have other plugins installed and enabled a default theme, in this case, could you please run a conflict test?
You can do this on Staging to not affect your live site, in case Staging can’t be created on your hosting, you can use a plugin like this one to create a Staging – https://ww.wp.xz.cn/plugins/wp-staging/
To run a conflict test, please try to deactivate all other plugins except for Forminator, set a default WordPress theme and then try to replicate the error.
Please let us know if it works.
Kind Regards,
Williams Valerio
Thanks for your reply.
I’ve tried your suggestions but it’s not worked.
I’m wondering if it is due to our servers? They use a CDN, could that effect the plugin?
I’ve set up a trial site on AWS and the plugin works OK on that.
Hi, I’ve just had it confirmed by our server team that a part of the Enterprise CDN’s auto-optimisation code seemed to break the plugin. Turning it off fixed the issue.
Thanks for your input, hopefully this might help in future if anyone else experiences a similar issue.
Hi @colouritin,
I’m glad to hear that you were able to resolve the issue.
Since everything is now working as expected, I’ll go ahead and close this topic. If you ever need any further assistance, please don’t hesitate to open a new topic—we’re always here to help.
Best Regards,
Nebu John
