- [x] Read the following guideline: https://docs.squidex.io/01-getting-started/installation/troubleshooting-and-support. I understand that my support request might get deleted if I do not follow the guideline.
I’m submitting a…
- [ ] Regression (a behavior that stopped working in a new release)
- [x] Bug report
- [ ] Performance issue
- [ ] Documentation issue or request
Our content editor managed to make a user with duplicate orcids and emails within our cloud hosted app (asap-hub). She mentioned that she told the UI not to update after saving as she has had problems with this before. Here is her bug report.
This morning I created a new user Pawan removed and when I hit save, Squidex asked if I wanted to reload content. I said no - because of past behavior that it overwrites the connection code being created. (This was a bug reported previously, and the response was to refresh squidex - but it still reoccurs from time to time),
Then there were TWO Pawan removed created (see screenshot). Obviously this is an issue.
I then moved one to draft -and sent Pawan an email to disregard one email and use the other one so that there wasn’t confusion. I clearly did not input Pawan’s name in twice in a row :-p.
The one that is in draft now is causing problems because it now is flagging that there is the same email and ORCID when I try to remove the connection - so I replaced the email with a bogus one, and removed ORCID and connection so that I could save it as a draft - but that you can at least have the page to figure out what happened:
It should not be possible to create two users with the same email and orcid.
Minimal reproduction of the problem
I can only report what my end user has reported above. I wonder if its having a user as draft which ignores constraints and then making that user live or something. It seems weird.
- [ ] Self hosted with docker
- [ ] Self hosted with IIS
- [ ] Self hosted with other version
- [x] Cloud version