Grant Hutchinson

> I can't promise it yet. We have quite a lot to do for 3.8 still. I imagine so! > As I wrote, a pull request for this is welcome....

Thanks for the examples. There are several terms and phrase variation I can add to the list based on these.

@mishrashutosh Phrases based on your comments have been added to the blacklist per commits aaaa94208fcc7c2f821577abb6a4b583ab2b95be and bf7b95cf85a7311eee22f06d23e932a9fdf0da45

@BdpnG0OrzW9esU6X Keywords relating to this issue have been added to the block list per commit c88e3ee

The above link is dead. Here’s an archived version: https://web.archive.org/web/20190308185254/https://wordpress.org/support/topic/3-spam-fixes-contact-form-7-v5-1/

Upon closer investigation, Gravity Forms does not directly support automated blocklist updates. It requires the use of one of the third-party plugins as [mentioned in the read me](https://github.com/splorp/wordpress-comment-blacklist#how-do-i-use-it).

As stated, I closed the issue because Gravity Forms Blocklist does not directly update the Disallowed Comment Keys field, but requires the use of one of the plugins already listed...

This issue has been resolved per commit 88ab507

Addressed the Discussion Settings information in the read me to reflect the various field name iterations in commit de3e332

Started changing “blacklist” to “blocklist” in the documentation per commit 9c265533d72c216eeb199fd493cb1db9ae0706db Still need to research what will happen regarding direct links to the blacklist.txt file if the repo name and...