NO BUG: Form submit error

Hi,

we wanted to try the native bricks form feature, we have setup everything but on the submit we get

{
“success”: false,
“data”: {
“type”: “error”,
“message”: “Es ist ein Fehler aufgetreten, bitte versuche es später noch einmal.”
}
}

We are not using any captcha on the form yet, so we can rule any form validation errors out from that side.
No data was saved to the db and no email was sent. We are using wp mail smtp and have no problems sending mails with it so far ( i wanted to replace Fluent Forms where the mail delivery has no issues so pretty sure we can rule that out )

Any optimization is turned off (Litespeed cache) and borlabs was/is turned off for rest aswell:

How can we debug this further?

regards

Hi @tos,

I’m not sure why, but I was able to successfully submit the form. I guess you fixed the issue already, or I checked the wrong one?

Best regards,
Matej

no thats the correct one - i still get the error - tried a different pc / browser
cleared cache etc. i have no idea

oh i just found the error:

when you use autofill in chrome it does not work - you need to manually enter the data in the fields - can u confirm this ?

Hmm,

ok, I guess I need to somehow trigger autocomplete. Because if I enter it like this (with double click and clicking on the suggested dropdown), it still works.

I guess you have the autocomplete that fills all the fields, right?

Also, do you maybe use honeypot?

Best regards,
Matej

yes, i saved lots of adresses and im using one of them and its filling out every field. and yes honeypot field is in the form and its a phone field, which field type would be better ?

Can you try to disable Honeypot field - just to test this? Or maybe check in dev tools, if there is any input inside.

Let me know.
Matej

yes when i remove the honeypot field it works with autofill

i tested a few fields now - with textarea it works - same error with text / pw / phone / email / url field - so as soon as the browser detects a field it can autofill the form fails because of the honeypot check.

Yeah, this happens when browsers ignore the autocomplete=off attribute and Chrome is really stubborn on this: https://www.reddit.com/r/webdev/comments/1buii9s/chrome_autofill_is_out_of_control/

I’m not sure what we can do here, as autocomplete=off is as close to the correct usage one as possible: How to turn off form autocompletion - Security | MDN.

You could try to change the attribute to something else, like new-password, but you will have to use Filter: bricks/element/render_attributes – Bricks Academy filter.

Best regards,
Matej

Ah i see - yeah well then thers nothing more you can do ( maybe add this note to the docs ? )

Ok what do you suggest “works” better against bots - changing the attribute on a field like phone or just use a textarea like i have now which does not get used for the autofill ?

cheers

If it works with textarea, then I think you should keep textarea.

When we introduced this feature, we automatically set the autocomplete to nope, which was better at preventing these kinds of things, but it had other issues: NO BUG: Autocomplete attribute in honeypot - #2 by Matej, so we changed it to official off and SOLVED: Bricks form accessibility issues - Radio and Checkbox - #8 by MichelyWeb
If you follow the first link above, you can also see how you can change it, if you like, to new-password, maybe.

Meanwhile, I’ll mark this topic as a no-bug.

Best regards,
Matej