-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
V9: Error when you try to invite user via backoffice #11453
Comments
Oh I just noticed this as well also v9.0.1 🙈 |
Looks like the error occurs because 9.0.1 doesn't set the sender address to the back-office user that's sending the invite anymore (which was a bug, as that might not be a valid sender address for the configured SMTP settings): #11266. Even though Umbraco Cloud adds a fallback for sending invitations without having SMTP configured, this doesn't expect the You can work-around this issue by at least providing the |
Yeah, except when the client don't use form or similar to send emails, but only need the feature to invite other users. Previous this required SMTP to be configured, but in a V8 version this changed, so the invite user button always was shown on Umbraco Cloud environments and thus didn't required further SMTP configuration to use the invite user flow. Not sure if it is related to this: #11575 |
@ronaldbarendse it doesn't seem to be enough just providing the It still throw this exception:
Update: Okay, it actually does seem to work now. Not sure if something was cached on production/live for some time. |
Which exact Umbraco version are you using? For example: 8.13.1 - don't just write v8
This is on Umbraco 9.0.1 Umbraco Cloud
Bug summary
When you try to invite a user from the backoffice you will get an error I have included the error in the specifics
Specifics
Unfortunately there is no error in the logviewer for this one
Steps to reproduce
Expected result / actual result
I would expect that I can invite users to the backoffice without any issues
This item has been added to our backlog AB#15057
The text was updated successfully, but these errors were encountered: