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

Member name discarded causing exception Services.MemberService.CreateMemberWithIdentity #12822

Closed
meyntony opened this issue Aug 10, 2022 · 1 comment

Comments

@meyntony
Copy link

Which exact Umbraco version are you using? For example: 9.0.1 - don't just write v9

v10.1.0

Bug summary

Services.MemberService.CreateMemberWithIdentity(
						username: "someUsername",
						email: "[email protected]",
						name: "Mandatory name",
						memberTypeAlias: "Member");

Even though the name is passed in the above call, it seems to be discarded and an Exception is thrown saying "Cannot save member with empty name"
image
"

Specifics

No response

Steps to reproduce

Services.MemberService.CreateMemberWithIdentity(
						username: "someUsername",
						email: "[email protected]",
						name: "Mandatory name",
						memberTypeAlias: "Member");

The above code snippet should be enough to throw the error described.

Expected result / actual result

Expected result: Member created successfully.

Actual result: Seems like the member is semi created in the database but not visible in the umbraco Backoffice
Exception is thrown saying "Cannot save member with empty name"

@kjac
Copy link
Contributor

kjac commented Dec 14, 2022

@meyntony thank you so much for raising this 👍 and sorry for the late response 😞

It seems this was fixed in #13020 so I'm going to close this issue now. Please feel free to reopen if the problem still persists.

@kjac kjac closed this as completed Dec 14, 2022
@kjac kjac removed the community/pr label Dec 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants