Just wondering if it's been discussed whether CAPTCHA module should provide a CAPTCHA field? I'm not sure what the implications are, nor whether this would be any better for admin usability.

I thought of this while building a multi-step entity form. If I use the current interface to add CAPTCHA to the form it appears on every step. If it was a field I could simply drag it to the end of the field list and use my current grouping method to limit it to the last page. I'm sure there is a simple way that I can achieve this in code, so I'm not looking for a solution, just wanting to start a discussion about CAPTCHA as a field.


rogical’s picture

Title: CAPTCHA as a field » Improve UX of CAPTCHA on entity forms

I think doesn't need this.

Fields are only used in entity forms, while currently captcha can be applied to all forms, so all we need is to improve UX on entity forms.

Some thoughts:
* better UX on multi-step entity form(as above said)
* easily to change the position of captcha by managing display of entities

soxofaan’s picture

Hi, I'm the maintainer, but to be honest, I don't have the time to lately to spend a lot of time on maintenance.

That being said and for your information: the 6.x-2.x and 7.x-1.x branches of the CAPTCHA module have been designed towards separation of the CAPTCHA as form element and admin UI. For example, it is possible to add CAPTCHA element to a form with just:

$form['nobotsplease'] = array(
   '#type' => 'captcha',

So it should be fairly straightforward to develop alternative UI's for CAPTCHA insertion and placement

also see #743056: Document how to add a CAPTCHA programmatically

soxofaan’s picture

Issue summary: View changes

Re-worded description slightly.