Snaptcha
ExpressionEngine 2, ExpressionEngine 3, ExpressionEngine 4, ExpressionEngine 5, ExpressionEngine 6
Back to this add-on's main page
View Other Add-ons From Brian Litzinger
Issues with Browser AutoComplete Feature
Support (Resolved)
msunickb
|
Posted: 27 June 2019 11:16 AM |
|
|
|
I have no had three client sites that say they’re getting the failed spam message from Snaptcha when the form is submitted. After researching, I notice that the failure comes most often when someone uses the autocomplete browser feature. I’m assuming it’s filling in the snaptcha value with something stored in their autocomplete entry. Can anyone give any advice how to avoid this?
As a sidenote, this tends to happen on shorter forms that aren’t asking for a lot of information. For example, if it’s a contact form that requests name, email and message it seems autocomplete fills in the snap field with other contact information that autocomplete stored like an address, city, etc.
Thanks!
Nick
|
|
|
PutYourLightsOn
|
Posted: 27 June 2019 03:54 PM |
# 1
|
|
|
Hi Nick, have you tried changing the “Field Name Prefix” to something other than “snap”? Autocomplete should generally only fill in fields it knows about and the Snaptcha field is appended with a random string, so I’m not sure that this is the real issue. See if it makes any difference though.
Ben
|
|
|
msunickb
|
Posted: 28 June 2019 11:00 AM |
# 2
|
|
|
I know, I was confused why the browser would do that as well but it was doing it for many people, and I was able to replicate with my own computer/browser.
I will change the default field name and see if that helps.
Thank you,
Nick
|
|
|
PutYourLightsOn
|
Posted: 28 June 2019 03:08 PM |
# 3
|
|
|
Ok, let me know if it makes any difference.
|
|
|
msunickb
|
Posted: 09 February 2021 02:41 PM |
# 4
|
|
|
Hi again,
Following up on this issue in EE6; still receiving the same behavior even when updating the default prefix in settings. Using version 3.0.0 of Snaptcha.
|
|
|
PutYourLightsOn
|
Posted: 09 February 2021 02:49 PM |
# 5
|
|
|
What value is being added to the hidden Snaptcha field when the autocomplete kicks in?
|
|
|
msunickb
|
Posted: 09 February 2021 05:20 PM |
# 6
|
|
|
From my test with this method, it’s getting an email address. I obviously changed the prefix value to ‘snapper’:
$(’.snapper’).children(‘input’).on(“change keyup blur input”, function() {
var $this = $(’.snapper’).children(‘input’);
console.log($this.val());
});
|
|
|
PutYourLightsOn
|
Posted: 10 February 2021 03:30 AM |
# 7
|
|
|
The hidden input field’s name should be `snapper_` followed by 9 random alphanumeric characters. On each page refresh it will be different, so I don’t see why autocomplete would ever be applied. Do you have the security level setting set to `High`?
|
|
|
msunickb
|
Posted: 11 February 2021 12:34 PM |
# 8
|
|
|
Right, that’s why I was confused as well. I have my setting set to Low currently.
|
|
|
PutYourLightsOn
|
Posted: 12 February 2021 09:26 AM |
# 9
|
|
|
Has changing the field name helped? I cannot replicate this issue.
|
|
|
msunickb
|
Posted: 15 February 2021 10:25 AM |
# 10
|
|
|
Unfortunately, it hasn’t helped. But, oddly, when I just set the ‘Name’ input on my form to autocomplete=“no”, I can use autofill on all other fields with no issue in submitting the form. Very strange.
|
|
|
PutYourLightsOn
|
Posted: 15 February 2021 03:36 PM |
# 11
|
|
|
Hmm that is strange, I wonder if the Snaptcha field was in the same fieldset as the `name` field?
|
|
|
msunickb
|
Posted: 22 February 2021 11:19 AM |
# 12
|
|
|
It wasn’t contained within the same <fieldset> element, but within a similar parent.. regardless, I’ve been able to get around the issue by disabling autocomplete on the inputs for the affected forms.
|
|
|
PutYourLightsOn
|
Posted: 22 February 2021 02:53 PM |
# 13
|
|
|
Glad to hear it!
|
|
|