Provide direct Mollom and CAPTCHA module support to allow authors to enable instead of administrators

There's not much we can do on the Webform side about webforms cluttering up the Mollom settings pages, Webform simply implemented the hook that Mollom provides. The entire support for generic forms in Mollom is a bit new, so I'm sure they're open to suggestions to improving the interface on that side of things. The permission to "Protect all Webforms by default" is something that should probably be controlled by Mollom, since it's ultimately responsible for determining when a captcha is shown.

On the Webform side of things, we could add an option under node/x/webform/settings to turn on/off Mollom (or Captcha module) on a per-form basis. We actually used to provide built-in captcha support, before the captcha module broke the APIs (twice) and ultimately just became a generic tool that Webform didn't need to have any integration with anyway, which was a relief because the APIs kept breaking.

However it seems that both modules have calmed down (slightly) and I'd be willing to re-integrate with them individually. In the mean time however, you're correct in that only users who have "administer mollom" permission can enable spam control on webforms.

Would be nice to have a link to the issue on the Mollom project about this:

#774188: Administration incapable of handling large amounts of (sub-)forms of a module

Updating title. Any users interested in submitting patches I'd be happy to look at them.

Postponing on that issue.

I'm not sure we need to postpone integration on the Webform side, where we'd need to add the "spam" column to the webform table. We can integrate with both CAPTCHA and Mollom and provide the option based on whichever service is available.

I'm thinking a simple checkbox such as:

[x] Provide a CAPTCHA on this form to prevent Spam

Or for Mollom:

[x] Protect this form with Mollom to prevent Spam

This checkbox would set the "spam" column in the database, and when the form was displayed it'd call the necessary API function to CAPTCHA-protect or Mollom-protect the form, regardless of administrator-defined options (though hopefully merging in admin-defined options if available).

Hm. Tough. You'd have to set a "default Mollom configuration" for all webforms then. And you most likely won't be able to use Mollom's text analysis (as that requires to manually enable individual form fields for text analysis). But of course, you should be able to relatively easy protect the form with Mollom's CAPTCHA only (which does not depend on a field configuration).

Normally, the Mollom module should be able to allow this, but I need to think about it.

And you most likely won't be able to use Mollom's text analysis (as that requires to manually enable individual form fields for text analysis).

Hm, I don't suppose we can pass into Mollom the configuration we want used? I think most users will always want analysis on all textfields, textareas, and e-mails.

This issue should also handle #980394: Captcha only on the last page of a Webform.

The checkbox is a great idea. I have a lot of editors who build their own forms and I'm unable to keep track of all of the forms that need to be added to the Mollom protected form list. It would be great if they could do this on their own.

Looks like the auto-protect functionality for webforms is now included in Mollom. Sweet :)

No idea what #10 is referring to, but there have been no changes to Mollom.

Instead, we're currently seeing an uptick of issues that claim that the author information is not properly mapped, which leads to improper content classifications by Mollom, as detailed in #1173570: Webform: Text analysis has author fields in post body -- however, that's a separate issue, not to be discussed here.

There won't be further feature development in the X.x-3.x branches.

Sure, new features go into the latest major/minor first. Why did you close this issue?