The Spambot Guard module enables you to add a simple addition question to common forms to help block automated spammers from polluting your site. It is much easier on users and in most cases is just as effective as a ridiculous image CAPTCHA.
The Spambot Guard module enables you to add a simple addition question to common forms to help block automated spammers from polluting your site. It is much easier on users and in most cases is just as effective as a ridiculous image CAPTCHA.
Comments
Comment #1
donpwinston commentedRepository view is screwed up for some reason but GIT says everything is up to date.
Comment #2
patrickd commentedNot screwed up, it's empty. ;)
Please have a look at the instructions how to use git on drupal.org.
Comment #3
donpwinston commentedLooks like it entangled with my other project XML Transform. Shouldn't they be in two different trees?
Comment #4
donpwinston commentedBought Gitbox from the App store. It looks like it did the right thing. Should be ok now.
Comment #5
patrickd commentedYep now it's there, but branch name is not following the release patterns.
I'm afraid that this project is too short to approve you as git vetted user. We are currently discussing how much code we need, but everything with less than 120 lines of code or less than 5 functions cannot be seriously reviewed. However, we can promote this single project manually to a full project. (adding tag)
Consider trying it again with another *little* more complex module, or - if possible - try to add more functionality to this module, so there's more to review.
Please take a moment to make your README.txt follow the guidelines for in-project documentation.
Please take a moment to make your project page follow tips for a great project page.
while waiting for an in-depht review of your module you can start out fixing some coding style issues detected by automated tools:
http://ventral.org/pareview/httpgitdrupalorgsandboxdonpwinston1487468git...
You can also get a review bonus and we will come back to your application sooner.
Comment #6
chertzogReview:
First you are working in the "master" branch in git. You should really be working in a version specific branch. The most direct documentation on this is Moving from a master branch to a version branch. For additional resources please see the documentation about release naming conventions and creating a branch in git.
(At least this has to be done before switching back to needs review)
After you get your branches taken care of, run your module through the Ventral PAReview and Coder.
On line 71 of your module file:
You should not directly translate variables. You should use a placeholder.
Then in .admin.inc you use this function:
to generate a form to list the forms you want to protect. What if i create my own content types? They cant be included if you hard code these options. Look into using node_types_get_types()" to generate a list of all the content types in the system.
Along the same lines, what about other forms? Custom forms from other modules, Webforms, node add forms for content types that users can create?
The CAPTCHA module does provide a math option, so i dont think this module provides enough differentiation to warrant a new module. If I am wrong on this, please explain the differences.
Comment #7
chertzog@patrickd Sorry, didnt mean to remove the tag. I was working on the review when you posted your comment.
Comment #8
donpwinston commentedI'll make the admin smarter.
Comment #9
donpwinston commentedIf the existing modules do this then I won't bother with this. I was just using this as an educational exercise to learn GIT and Drupal anyway.
Comment #10
donpwinston commentedThere's a similar technique in the CAPTCHA Pack module. Also, there are other techniques like hidden questions, identify a missing letter, and identifying a word that does't belong in a list that are also better then the image CAPTCHAs. I'm closing this. I'll think of something else to do.
Comment #10.0
donpwinston commentedtypo
Comment #11
avpaderno