Skip to content
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

This email is already taken! #1133

Closed
1 task done
Hammemo opened this issue Dec 4, 2024 · 3 comments
Closed
1 task done

This email is already taken! #1133

Hammemo opened this issue Dec 4, 2024 · 3 comments
Labels
awaiting triage This issue needs to be reviewed bug Something isn't working

Comments

@Hammemo
Copy link

Hammemo commented Dec 4, 2024

Description

Can't save any changes to user settings due to "This email is already taken!" error message when email is blank.

Version

2.1.0

Steps to Reproduce

  1. Go to users. 2. Select a user. 3. Edit settings. 3. Make changes or don't it makes no difference as long as email is blank. 4. Click Save Changes. 5. Receive error message saying "This email is already taken!" and changes are not saved.

Screenshots

Screenshot

Logs

No response

Platform

desktop

Device

Dell XPS

Operating System

Manjaro

Browser

Firefox

Additional Context

No response

Code of Conduct

  • I agree to follow Jellyseerr's Code of Conduct
@Hammemo Hammemo added awaiting triage This issue needs to be reviewed bug Something isn't working labels Dec 4, 2024
@Fallenbagel
Copy link
Owner

Fallenbagel commented Dec 4, 2024

Please do not open duplicate issues.

Duplicate of #1094 and #1127.

This issue is already fixed in #1096.

@Hammemo
Copy link
Author

Hammemo commented Dec 4, 2024

Issue is not fixed. You shouldn't be able to make a user at all without an email address if you require one to make any changes to it.

@Fallenbagel
Copy link
Owner

Fallenbagel commented Dec 4, 2024

Issue is not fixed. You shouldn't be able to make a user at all without an email address if you require one to make any changes to it.

Issue is fixed. As literally seen by the PR i just linked. It's NOT released yet. The fix does NOT exist in 2.1.0. You're using 2.1.0.

Like I mentioned previously, please do not create duplicate issues. If the issue exists AFTER the fix is released, mention in the original issue. Not new ones.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting triage This issue needs to be reviewed bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants