-
-
Notifications
You must be signed in to change notification settings - Fork 469
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
Newer TLDs are considered invalid. #435
Comments
@kp3nguinz As there are some frontend validation to validate a email id before adding it. |
@kp3nguinz As I tested with Test@test.com.group, It is working fine. |
@kp3nguinz As we have tested the current release of project it is supporting such emails !! We are closing this if you are still facing the issue please reply here on same thread or can generate a new issue !! |
The new TLDs do not seem to be validated in the Helpdesk Configuration wizard. I am on release 1.0.16. When I created a super admin account as prompted within the installation wizard, my email address (which ends in .agency) was not accepted. I tried .group too and that wasn't either. "Invalid email" error message. Workaround So my assumption is, custom TLDs are accepted under Edit Profile, but I think there is still a bug with the installation wizard. |
As we check we found that regex is not able to accept new email TLDs to be validated in the Helpdesk Configuration wizard. If you found any error or any issue, please let us know |
Bug report
Title
Just a quick sentence to brief your trouble with UVDesk or something associated with it.
Please be calm, short and emphasize on points.
Email validation on setup does not support abnormal TLDs (in my case, .group)
Issue Description
Description helps the developers to understand the bug. It describes the problem encountered or some after effect of some kind.
My email is showing as not valid (which ends with a .group), but my throw away does (.com TLD)
Preconditions
Please provide as detailed information about your environment as possible.
Using the latest build in docker as of today (I built from your main branch).
1. framework Version.
2. Commit id.
Steps to reproduce
It is important to provide a set of clear steps to reproduce this bug.If relevant please include code samples.
Expected result
Tell us what should happen.
Actual result
The text was updated successfully, but these errors were encountered: