Hi, thank you for reaching out to us. Could you please share a short video of the steps you are taking and the issue occurring on your end, so we can review it accordingly?
Thread Starter
mseka
(@mseka)
hi, thanks for your reply.
it affects when I add/edit the option on the dropdown field, when I click “save form”, it only loads and never succeeds.
but when I deactivate your plugin, it works fine.
https://bit.ly/40xAxDG
I’m not sure why this happened.
But now, I can save it by enabling “no conflict” mode from the Gravity Form setting.
Still, the looks on the Gravity Form editor are a bit different than normal (maybe some CSS/js are automatically disabled on the editor page).
Thank you
Hi, Thank you for sharing this. We are currently checking this concern and will provide you an update shortly. We kindly request your patience in the meantime.
I’m also having the exact same issue (conflict with gravity forms). To add more information, I’m getting this JS error in the web dev console:
scripts-admin.form-e…7733f35874.min.js:1 Uncaught TypeError: Cannot set property Type of [object Object] which has only a getter
at t.value (scripts-admin.form-e…5874.min.js:1:11603)
at t.value (scripts-admin.form-e…5874.min.js:1:11616)
at t.value (scripts-admin.form-e…5874.min.js:1:12161)
at t.value (scripts-admin.form-e…5874.min.js:1:11150)
at 281.8962838….min.js:1:855
at Array.forEach ()
at e.value (281.8962838….min.js:1:809)
at HTMLButtonElement. (scripts-admin.form-e…5874.min.js:1:10653)
My best educated guess is that something in the check email JS is conflicting with Gravity Forms because when I turn on “no-conflict” mode in Gravity Forms or disable the check email plugin the issue no longer happens.
Hi @mseka & @cmyee ,
Thank you for sharing this information. We have been able to recreate the issue and it will be fixed in the upcoming update. Until then, we kindly request your patience.
GitHub Ticket.
Hi All,
Hope you are doing well.
We have just released an update version 2.0.5, in which we have addressed this concern. Kindly update the plugin to the latest version, clear the cache once, and give it a try.
