Word Blocking Requests

  • Resolved webwildfire

    (@webwildfire)


    11 months, 2 weeks ago

    Hi there!

    I have some words a client wants blocked to prevent spam or unwanted emails in a contact form. reCaptcha has helped a lot, but a few annoying emails are still coming through.

    I’m finding the “Keyword Based Restriction” doesn’t work, unless the keyword is the only word in the text box. I’m not sure if that’s intentional or a bug?

    I ended up using the Advanced Form Validation. Because one abbreviation might show up within other words, I had to use regex matching via \b[Ww][Oo][Rr][Dd]\b to cover it, as opposed to just checking for “contains”. It’d be nice if there was case-sensitive option for regex, or some word check option that would cover it without writing regex.

    It would also be great if, instead of showing an error message to the user, the form appeared to submit but didn’t. Is that possible?

    The one way I can think to do it is to add conditionals to the email notifications and integrations individually. That’s a lot of work. Plus, the regex matching wouldn’t work since there isn’t a way to say “don’t match this” with it.

    Am I missing something? Or do you have any advice?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Abul Khoyer

    (@hellokhoyer)

    Hello @webwildfire,

    Restrictions based on keywords work with comma-separated values. So, if you have multiple words, you would need to separate them with a comma.

    There is no option to have “not contains” / “do not match” check in advanced form validation.

    Also, it’s not possible to show a successful submission without actually processing the data.

    Regarding adding conditions to the email notifications and integrations individually, this can be possible – you can set conditions there individually.

    Thank you.

    Thread Starter webwildfire

    (@webwildfire)

    Hi Abul! Thank you for taking the time to address my post.

    Restrictions based on keywords work with comma-separated values. So, if you have multiple words, you would need to separate them with a comma.

    You’re misunderstanding my issue. You’re thinking I’m saying I can only use 1 word in the restrictions list, which is not what I meant.

    When I tried it, I just had the 1 word, and it would only block it if that was the only word used in the text box in the form itself. A user could submit a sentence with the word, and it’d pass.

    I haven’t tried it again recently, but if you’re unaware of the issue, it probably needs to be looked at.

    And how sensitive are those keyword restrictions? Case sensitive or case insensitive? Word matching like I was doing with regex or no?

    There is no option to have “not contains” / “do not match” check in advanced form validation.

    Also, it’s not possible to show a successful submission without actually processing the data.

    Regarding adding conditions to the email notifications and integrations individually, this can be possible – you can set conditions there individually.

    But as I said, the conditions for email notifications and integrations doesn’t work for me because I can’t say “don’t send it if it has this word” if I have to match with regex. So it sounds like I’m correct that the conditions are too limited for what I am considering.

    So I would like to suggest adding more options to control these things. The existing conditions are not sufficient for full control.

    The only thing is, if you do that, then the entries still get stored.

    • This reply was modified 8 months, 2 weeks ago by webwildfire.
    Plugin Support Abul Khoyer

    (@hellokhoyer)

    Thanks for the clarification, @webwildfire. Currently, there is no workaround I can suggest to you. I’m taking this as an improvement suggestion and let our R&D team know about this. Hopefully, they will look into it.

    Thank you.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Word Blocking Requests’ is closed to new replies.