https://forge.joomlapolis.com/https://forge.joomlapolis.com/favicon.ico?17095821032017-09-14T21:17:38ZJoomlapolis forgeCB AntiSpam - Bug #6679: Honeypot only mode fails validationhttps://forge.joomlapolis.com/issues/6679?journal_id=171162017-09-14T21:17:38Zkrileonkrileon@joomlapolis.com
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>Rejected</i></li><li><strong>Target version</strong> deleted (<del><i>3.1.0</i></del>)</li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>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.</p> CB AntiSpam - Bug #6679: Honeypot only mode fails validationhttps://forge.joomlapolis.com/issues/6679?journal_id=181852018-04-26T16:35:59Zkrileonkrileon@joomlapolis.com
<ul><li><strong>Status</strong> changed from <i>Rejected</i> to <i>Resolved</i></li><li><strong>Target version</strong> set to <i>3.2.0</i></li></ul><p>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.</p> CB AntiSpam - Bug #6679: Honeypot only mode fails validationhttps://forge.joomlapolis.com/issues/6679?journal_id=183332018-06-18T20:23:28Zkrileonkrileon@joomlapolis.com
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>