Hello,
Here's a form which have close date/time and has captcha.
This form has expired. I can see the message I specified (form closed message) but still there is the captcha challange.
Please find attached screenshoot.
(webform 8.x-5.1)
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | 3035054-10.patch | 13.96 KB | jrockowitz |
| #8 | 3035054-8.patch | 11.79 KB | jrockowitz |
| #6 | 3035054-6.patch | 11.21 KB | jrockowitz |
| #5 | 3035054-5.patch | 3.88 KB | jrockowitz |
| #4 | Contact Webform Demo Site.png | 337.85 KB | jrockowitz |
Comments
Comment #2
jrockowitz commentedAre you adding the CAPTCHA as a webform element? or as a global behavior (/admin/config/people/captcha/captcha-points)?
Comment #3
kepesv commentedAs global behavior.
I've just tried as element now, it is a new - previously unknown - way for me I can add a captcha to the form .
This is solved the problem, thank you for the hint, You are Great.
Even so I think it could be useful for many people if it could be working properly as global behavior too.
Comment #4
jrockowitz commentedI am not seeing any easy to fix this problem. The only immediate solution I can think of is adding a warning to the CAPTCHA placement details.
Comment #5
jrockowitz commentedBecause a webform attached to nodes can have multiple form IDs (one for each node) it makes more sense to encourage everyone to add a CAPTCHA element to a webform instead of a CAPTCHA point.
The attached patch replaces the CAPTCHA module's link with an add/edit a webform specific CAPTCHA element.
This approach is going to require a change record.
Comment #6
jrockowitz commentedComment #8
jrockowitz commentedComment #9
jrockowitz commentedHere is the final patch.
Comment #11
jrockowitz commentedI committed the patch. Please download the latest dev release to review.