Hey @darrylbosch – Thanks for reaching out!
When you have sometime, can you please try the steps described in our detailed guide on how to test for plugin/theme conflicts and see if that helps?
Kindly,
Hi @darrylbosch – Sorry to hear about the trouble you are facing here!
When you get the chance, would you mind sharing the form URL with us so that we can take a closer look?
Thanks,
Thread Starter
Anonymous User
(@anonymized-20831043)
Hi @prashantrai. I followed the advice in your link but the error persists. I deactivated all plugins, completed the form, and the same error is generated. I switched from OceanWP theme to Twenty Twenty-Two theme and the same error is generated.
Hi @niksebastian, this site is under development and contains proprietary information that is not ready for public viewing yet, so I am unable to share the URL publicly. Thanks for your offer, though.
Hey @darrylbosch – Thanks for following on this ticket!
Looking at the error message, it seems to be related to the GDPR field. When you have sometime, can you please check and let me know if you’ve enabled GDPR field on the form?
Kindly,
Thread Starter
Anonymous User
(@anonymized-20831043)
Hello again, @prashantrai.
Yes, I do have GDPR enabled.
I actually found a solution to the problem. I thought I would try to disable the different anti spam options to see if that made a difference. My settings included an option to enable an anti-spam honeypot. I read through some more documentation and learned this this option is only available on forms created prior to plugin version 1.6.2.
So, I created a new simple contact form identical to the original, enabled anti-spam protection and Akismet anti-spam protection (the anti-spam honeypot option was no longer available) and now it works fine without the error. This works on both my live and local development sites.
I guess the form was too old for the updated plugin.
Thanks for your help and suggestions. Maybe this will help others.
Hey @darrylbosch – Thanks for sharing the details, and I’m glad you were able to fix the issue. If you have any questions, please feel free to reachout.
Kindly,
