-
Notifications
You must be signed in to change notification settings - Fork 323
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
The parameter PWP__SIGNUP_EMAIL_REGEXP does not work #2082
Comments
Hello @CorentinDeBoisset, thanks for contributing to the Password Pusher community! We will respond as soon as possible. |
Hi @CorentinDeBoisset - The regexp is applied here. It plugs into Devise which is the authentication system in use. I just retested it myself and it works here locally: Are you sure you applied the environment variable correctly? Let me know - I can explain in more detail if you like but really the regexp is just passed through into Devise. |
Use single quotation |
That's a good point @anikwai - @CorentinDeBoisset have you tried with single quotes? Are you still having this issue? |
Hi @CorentinDeBoisset - let me know if this is still an issue for you. If not, I'll close out this issue soon but you can re-open or file another anytime. I'd be happy to help out. |
I had to do it without quotes at all..... (PWP__SIGNUP_EMAIL_REGEXP) |
Quotes are required as it's a string that is parsed by the |
馃悰 Bug Report
When setting the environment variable
PWP__SIGNUP_EMAIL_REGEXP
, it has no effect. When searching in the code for the usage of the string"regexp"
the only matches are the declaration of the parameter but it does not seems to be used anywhere.馃敩 How To Reproduce
Steps to reproduce the behavior:
PWP__DISABLE_SIGNUPS=false
andPWP__SIGNUP_EMAIL_REGEXP="\A[^@\s]+@domain\.tld\z"
Code sample
N/A
Environment
Where are you running/using Password Pusher?
If applicable, what version of Password Pusher? 1.35.0
Screenshots
N/A
馃搱 Expected behavior
There should be an error when trying to sign up using an email that does not match the regexp.
馃搸 Additional context
N/A
The text was updated successfully, but these errors were encountered: