-
Notifications
You must be signed in to change notification settings - Fork 4
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
User email prompt/collection issue #479
Comments
Also, let me know if this is a problem with Salsa on our end. |
@deraj1013 This is the expected behavior. I will send you testing instructions that outline the full spec via email, as they contain the login for the staging site. |
I'll check through the instructions. The user (and I) are not getting the verification email. That's not how it's supposed to work, is it? |
If there is no email, then things aren't working as expected. I will open an email thread with you and John, as we will need some budget to debug and repair the issue. |
Sounds good |
So it looks like the email came through to my account about four hours after I submitted it. It may be an issue on the end of our user rather than the system. |
The same thing happened to me, when I resubmitted my email as a test! Think the message came through the next day. Picking this up now, @deraj1013. |
TODO: Swap in SendGrid creds prior to launch. |
For posterity, this was mostly addressed by datamade/django-salsa-auth#9. |
Update: We've switched over to SendGrid for the launch. |
A user reported an issue with the email collection prompt that I was able to duplicate in incognito mode in my browser with an email that has not been used to sign up for the database. Essentially, when the user hits a maximum allowable search, it prompts him to enter his email. He does, and then the prompt tells him to check his email for a verification message.
I was under the impression that the email information was now being handled through a cookie rather than the email verification. Let me know if I'm wrong, and if you have any idea what the problem is here. Also, if you need more information from me, let me know.
The text was updated successfully, but these errors were encountered: