Plugin Author
Franky
(@liedekef)
Preventing autofill of a visible field is useless. Also, your browser happily ignores any indication of autocomplete of formfields most of the time anyway.
Also, I don’t understand “the form will not appear because there’s no #_PASSWORD field added”. The form appearing or not has nothing to do with autocomplete.
Thread Starter
eltebe
(@eltebe)
Okay, I try to explain it:
In any browser there is a “save password” feature.
If we save wordpress admin login password, the browser will prefill your RSVP password field, because theres no autocomplete=”off” attribute on it.
Because of this: every new event will be protected by the administrator’s login password (that prefilled automatically by the browser) and the RSVP password field must be deleted every time when a new event created or edited.
You can use autocomplete=”off” attribute, it supported/partial supported by main browsers.
And the second part is:
We do not want to protect the booking form with a password, so we did not insert the #_PASSWORD placeholder into the form. Thats ok, while the RSVP password field not filled in accidentally (by the browser: see above).
(Otherwise the booking form on the event page will not show – just an error message that says “#_PASSWORD is missing”).
-
This reply was modified 7 years ago by
eltebe.
Plugin Author
Franky
(@liedekef)
Ok, in the backend your question makes sense 🙂
I’ll add the autocomplete=off there (but like I said and the post you found too: it is no guarantee at all 🙂 )
Plugin Author
Franky
(@liedekef)