gotcha for D6

Thanks for the code. Well, I have to jump through Windows hoops to view this patch, so it will be a bit.

I am debating on whether to continue this module with the introduction of Mollom and the delays in Spam. Comments are welcome.

Personally I'm happy with what gotcha does and have applied the principles on non-drupal contact forms and it has stopped the garbage there as well as a couple of drupal sites.
Mollom is certainly very impressive as I would expect from Dries and is the right tool for for high profile, high activity multi user sites but for the sites I'm dealing with it would be overkill.
I would suggest that gotcha just needs a bit of a cleanup, a couple of added admin settings (the ability to change weight and fieldname) and that would do nicely.

Any word on an 6.x implementation?

First I have to upgrade it for Spam V3.

+1 for upgrade please.

My site is non-English and Mollom doesn't quite work (or is it just me?).

Thank you,

Regards

I will get to this when I can.

How does effect screen readers? For instance a visually impaired or blind person visits the site using a screen reader. The screen reader still "see" the display:none field as screen readers ignore CSS rules and the person using the screen reader will then fill out the field and thus their submission will erroneously be labeled spam.

I ask because the sites I work on must follow section 508 for accessibility and thus be able to work with screen readers.

+1 Mollom is cost based. I would rather something free for our NPO clients.

For now I guess I will install Captcha once again...

Any response to the accessibility issue?

@TheresaB: is there some way to mark a field to not be read that would not also be used by a spambot to skip it?

@mdlueck: Sorry. If anyone is willing to fund this, then its priority will go up.

Nancy, no not by using CSS. As you probably know you can either define a display:none;, which is used for such things as skip navigation to facilitate screen readers not having to constantly repeat a site's navigation before getting to the content of a page, and visibility: hidden;.

There is no way to hide a field, that I know of, so that a screen reader will not "read" it. What you see when you turn off all css on your site is what the screen reader will see and the order it will see it in.

I want to note I so appreciate your efforts in this, in providing a way to help curb the spam bots from making a mess of one's site and for those that do not have to comply with accessibility standards this is a very good way to differentiate between whether a human or bot filled out the form.

Thank you Nancy for all your work with this module.

Doesn't it have a description that says to skip the field? I can't remember.

If your speaking of a "skip nav" no, just a display:none; is all. Screen readers completely ignore CCS styles.

The only other way to skip anything is the alt tag for images if you do not define an alt tag the screen reader will read the name ofthe image, which not only does not convey any useful information to the person using the screen reader but will be very irritating if the site makes use of graphics for visuals and/or layout. The alt tag is then used to provide a short description which will be read instead of the image name and conveys meaning to the person using the screen reader. If the graphic is only being used for decorative or lay out a empty alt tag will cause the reader to "skip" reading the image all together, such as alt="".

There is no command, that I am aware of that will instruct a screen reader to "skip" an element in the code. I wish there was as it would make my life easier. ;)

adding accessibility tag

See the note on the project page. I have one site left using this, but as soon as I can, it will be switched to Mollom. If someone wants to take thsi module over, open a "task" issue.

A development version of gotcha for D6 is now in CVS.

6.x-1.x-dev is now available under View All Releases

I don't see Mollom as an replacement for Gotcha. We run a site, where people submit confidential information via web form. To limit the potential risk of disclosure we can't forward the form to any other party than recessary.

An improvement for this module would be a local honeypot page. That can be a hidden Page (preferably the first Link on the page), which contains a link and a formular, which will blacklist the poster immediatly on access. Search engines can be prevented to index the page and to follow the link by setting the robots meta tag to noindex,nofollow.

I see this is moving to D6.. so this is old news, but the project page asks for comments about using Mollom.
My tiny comment is; Have you looked at text in the e-mail that is received when using Mollom? well, that is why I won't use it. My web site subscribers/users would see that and delete their membership.

I"m not a big fan of Captcha and forcing my users to fill out a form, but the spam module is hard to configure.
I never had a problem with the Captcha and re-Captcha modules, so I'm not sure why I would use Mollom ever.
This idea is pure genius, until spammers get around it. But until then I will use it with full force.

Is there anyway to integrate this into the comments? I'm only having spam issues with comments.

+1 for continuing this module. Don't give up!

Gotcha works on the form_id, it is currently set to work on
contact_mail_page
contact_mail_user

try adding

immediately below

in function gotcha_form_alter() which is circa line 118 in gotcha.module

I just did a quick test, the hidden field appeared in the comment form so it should work ;-)

It would seem this would work but for one small problem:
If you have ajax comments installed you get this error:

An error occurred.

And then it hangs.

Looking at line 338:

It is apparent that its trying to submit to the mail page but since this is comment it won't work?

I opened up a separate issue for the inclusion of comment form for gotcha. #638626: Gotcha for Comments