-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Add re-capture to subscribe and contact form #47
Comments
@ElliotForWater/elliotforwater-team Hi, I've been reading over the project documentation and got the development server running. I would love to help contribute! Can I be assigned to this issue? |
@karlrez hi and thank you for your interest in contributing to Elliot For Water. I have assigned the issue to you, feel free to work on it and let me know if you have any further questions or feedbacks. |
@gsambrotta Hi, I just want to give an update on this and have a question about the UI. I chose to use reCapcha v2, as it requires the user to interact more and it also generates a token which we can send to the backend: https://developers.google.com/recaptcha/intro Are you able to elaborate more on how this should look on the frontend? Would you rather the recapcha to toggle visibility and only show when a user tries to submit their email? Do you have any suggestions on size location of the recapcha? Let me know your thoughts. |
Hi @karlrez! Happy to read about your progress. It looks good already :D I was wondering, why did you choose reCaptchav2 Robot instead invisible one? What do you think? |
I agree! Apologies, I guess I had misread the feature request and thought we wanted the one with more user interaction. |
As an Elliot For Water User:
When I click the Subscribe Bbutton or Contact Form Send button
Then I should be presented with the "I am not a robot" re-captcha.
https://www.google.com/recaptcha/about/
It maybe also possible to re-implement the Aniti Forgery Token using React and WebApi based on this example;
https://stackoverflow.com/questions/11476883/web-api-and-validateantiforgerytoken
Either approach would be sufficient.
Give priorities to the approach that don't automatically fill in the re-captcha and avoid the user to interact. If possible.
The text was updated successfully, but these errors were encountered: