Feature #308
Support for overriding the reCaptcha field validation
| Status: | Closed | Start date: | 11/10/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | 11/14/2010 | |
| Assignee: |  George Notaras | % Done: | 100% | |
| Category: | - | Estimated time: | 2.00 hours | |
| Target version: | 0.3.2 |
Description
Reasons for overriding the reCaptcha field validation:
- app testing.
- use of the app, that incorporates django-recaptcha-works, in a secure environment without messing with the code.
- make the reCaptcha field respect the
required=Falseattribute. Disadvantage: editing the code is required - add a new setting that enables or disables the reCaptcha field globally (all forms that use it). Disadvantage: it is not possible to disable the field on a per form basis.
History
#1
Updated by George Notaras over 2 years ago
- Status changed from New to Assigned
- Assignee set to George Notaras
- Target version set to 0.3.2
#2
Updated by George Notaras over 2 years ago
- % Done changed from 0 to 10
- Estimated time changed from 1.00 to 2.00
Regarding the second resolution, investigate which is the best way to deactivate a form field based on a setting.
- evaluate the setting in
RecaptchaField.__init__() - evaluate the setting both in
RecaptchaField.clean()andRecaptchaWidget.render()
#3
Updated by George Notaras over 2 years ago
- % Done changed from 10 to 90
#4
Updated by George Notaras over 2 years ago
- Status changed from Assigned to Closed
- % Done changed from 90 to 100
Finally added support for checking both the required=False field attribute so as to be able to override the validation on a single form, and also added the new RECAPTCHA_VALIDATION_OVERRIDE setting, which causes validation overriding for all reCaptcha protected forms.
