I gave permission to use the site-wide contact form for anonymous users, then enabled the CAPTCHA point for it. However, the CAPTCHA doesn't appear on the Contact form, but it works on the User Registration Form.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | Screen Shot 2017-06-01 at 1.20.11 PM.png | 85.42 KB | gg24 |
| Screen Shot 2017-04-01 at 09.39.54.png | 34.26 KB | aonsquared |
Comments
Comment #2
ankur.addweb commented@Arthur, I have checked captcha functionality with same version and it works fine for me.
Make sure you are adding a FORM-ID instead of form machine_name while adding a new captcha point [admin/config/people/captcha/captcha-points/add].
Comment #3
gg24 commentedHi @aonsquared,
I tried reproducing the issue but couldn't find it. Please mention the steps to reproduce this issue.
Testing steps are as follows:-
Attaching captcha screenshot too taken from Anonymous user's account.
Thanks!
Comment #4
gg24 commentedScreenshot for comment #3.
Thanks!
Comment #5
gallegosj commentedI'm experiencing this same issue. I created a custom form using the core contact module, but I can't get CAPTCHA to show up on it. It shows up fine for user registration and user login. By the way, what is the FORM ID and how is it different from the machine name?
Comment #6
adamps commentedI had the same problem, and fixed it by following instructions in #3.
My problem was that I had enabled the "contact_message_feedback_form" captcha point that was provided by default.
The resolution was to create a new CAPTCHA point as per step 4 of #3. The captcha point needs to be contact_message_XXX_form, where XXX is the machine name - you can see the machine name on the "Edit contact form" page admin/structure/contact/manage/XXX.
The process seems much less intuitive that it was in D7, where things worked well with a default install. Here are my suggestions
Comment #7
gallegosj commentedGreat catch @AdamPS! A new captcha point using the format you provided fixed the issue for me. Thanks! I agree with your suggestions.
Comment #8
elachlan commentedComment #9
adamps commented@elachlan Please can you explain the reason for setting this to fixed?
In #6 I made 3 suggestions - have they been done? If not, would it make sense to raise a feature request for them?
Comment #10
elachlan commentedIf you could raise a Change Request and link it, that would be great.
Thanks.
Comment #12
adamps commentedSorry for the delay I lost track of this issue. I have now raised two new issues: