Last updated by miro_dietiker on Wed, 2010-04-28 07:01
Mollom recently added extended user configuration to allow per form_id settings.
Mollom settings are clean and feature rich, but don't consider some use cases.
See initial issue:
http://drupal.org/node/774188
Read more about thoughts and extend your usecases.
The extension of mollom is designed to be a super administrator configuration task. What we need is a workflow that allows admins to put captchas into user generated forms entities like webforms.
Either allowing us to enforce captcha handling (all added webforms will have captcha), or to bring the captcha configuration to the user form creation (all user generated forms).
This all could happen in mollom.module but much more could also be a general captcha api to tie captcha configurability together - so all captcha implementations implement the same api to deliver captchas only.
Per form (form_id) use cases:
- Protect registration form
- Protect node blog add form
- Protect a single webform
- Protect a single poll
- ...
This is what mollom currently introduced. For every created form (form_id) you need to enable the captcha itself.
Per entity use cases:
- Using webforms.module we want to protect all
- Protect all polls (user generated)
- Using node add (for anonymous) we want to protect all node form submissions
- Same for contact forms
- Same for comment forms
- Protect User forms
- ...
The per-entity configuration reduces overhead in two ways:
- An administrator can define a general rule to protect e.g. all webforms. Less rules.
- If (unprivileged) users add more webforms no additional administrator configuration is needed for form protection. User activity independence.
User centric form creation use cases:
- Polls (advpoll, poll)
- Webforms (webform)
Enabling all anonymously submittable forms to be captcha controlled would be too aggressive. At least one should be able to disable some forms. However this would create processing overhead (although following some ideas like drupal does in e.g. block visiblity) compared to the simple per-form or per-entity lookup with configuration.
Feel free to extend this wiki if you have further ideas in how to generalize the idea captcha handling.