You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A user is able to access the website for a long time (at least days) and contribute to projects, without verifying the email used to create an account.
To Reproduce
Create an account on mapswipe-web
Stay logged in
Expected behavior
A user creates an account and is prompted to verify their email.
Then;
The user either does not gain further access to the website untill the email is verified.
or
The user only gains access for a limited time (20 minutes given the email verification message states it could take this long to recieve the verification email in your inbox) after which they are prompted to verify and/or scope e.g. they are able to complete tutortials or browse through the available projects (but are unable to contribute to them) while they wait to recieve the verification email.
Desktop:
OS: [Windows 10]
Browser [Firefox]
Version [126.0]
Additional context
It appears that a user cannot log-out and back in again without verifying the email account used to create the account, however, please confirm that this is indeed the case.
The text was updated successfully, but these errors were encountered:
Release notes from v0.1.0 state "Allow unverified users to access projects and contribute (configurable)" this may be reason enough to close this issue.
@ofr1tz is the configuration be the reason why the website behaves this way?
Describe the bug
A user is able to access the website for a long time (at least days) and contribute to projects, without verifying the email used to create an account.
To Reproduce
Expected behavior
A user creates an account and is prompted to verify their email.
Then;
or
Desktop:
Additional context
It appears that a user cannot log-out and back in again without verifying the email account used to create the account, however, please confirm that this is indeed the case.
The text was updated successfully, but these errors were encountered: