• what’s wrong guys, it doesn’t work anymore.
    Plus, it’s stupid to set it up for each and every form. Make it a general setting.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Steve Jones

    (@stevejonesdev)

    It was working up until just recently. I’m assuming since the latest Gravity Forms update. We will look into the issue and push out a fix.

    I wouldn’t call the current implementation stupid as it actually give the user the most flexibility. Blocked domains are not set at the form level but rather the field level. This allows different domains to be blocked in different email fields on the same form. Now having a form setting or even a global (all forms) setting might be a good addition.

    We provide this plugin free of charge and do our best to maintain it. Please be patient and respectful and we’ll get this fixed shortly.

    Thread Starter gaetaneksz

    (@gaetaneksz)

    Yeah, I know Steve, but at some point you got bored with that bunch of plugin not working, my comment is mainly to say “hey that needs to be fixed now”
    of course thanks for that,
    ps I found a solution with that : https://gist.github.com/ajskelton/402c3c0c1da5edbbf7e4022d982810c5 and it does the job, all I ask

    Plugin Author Steve Jones

    (@stevejonesdev)

    @gaetaneksz, I’ve tested with current versions of WordPress, gravity forms and the Gravity Forms Block Email Domains plugin and it appears to be working. Can you provide any information to help troubleshoot the issue? Are you running current versions of the plugins. There may be a plugin conflict. Specifically are you using any other Gravity forms add-ons?

    Thread Starter gaetaneksz

    (@gaetaneksz)

    using lots of them actually, trouble is not only with your plugin. It was not working with blacklist emails plugin as well (have a look there is a general list of locked domains)
    here the list of plugins/addons we use : https://association.confidencesdabeilles.fr/wp-content/uploads/2022/09/Capture.jpg
    but the code found on github does the job perfectly.

    Plugin Author Steve Jones

    (@stevejonesdev)

    This was most likely a plugin conflict plus you’re not running current version of many of those plugins as well.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘doesn’t work at all’ is closed to new replies.