Bug #6679
closed
- Status changed from Assigned to Rejected
- Target version deleted (
3.1.0)
- % Done changed from 0 to 100
Works fine in all test cases. My guess is something may have been filling the honeypot input (browser autofill?) or the honeypot name was conflicting with an actual field.
- Status changed from Rejected to Resolved
- Target version set to 3.2.0
Was able to find and confirm the cause. It was due to ->input not caching the captcha instance, which was only happening in ->captcha. Now when trying to grab the input or the image it will properly generate a captcha code and cache as needed.
- Status changed from Resolved to Closed
Also available in: Atom
PDF