You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Did you search the issue queue for existing issue? Search issues
Issue Description
The email sent when you invite an admin user to your shop has a button. When you click that button, it doesn't bring you to a page to accept the invitation or explain how to register and accept.
Steps to Reproduce
Setup
Log in as operator.
Edit Shop settings and make sure the shop email address is [email protected]. This address is verified to send emails through the Reaction testing SES account. Other addresses may not work.
Go to the operator user profile page and make sure you have a real email address. You can use something like <yourname>[email protected].
Enter correct email service credentials on Email page. Make sure the indicator is green.
Reproduce
Log in to operator UI
Go to Accounts screen
On "Add Admin User" card, add a new user with a real email address. For example, <yourname>[email protected]
Click the button in the "You are invited to join" email.
Possible Solution
Need to figure out what should happen or what previously happened when this worked, and then make it happen again.
Versions
2.0.0 RC 11
The text was updated successfully, but these errors were encountered:
Cannot reproduce this error. I was able to invite a new shop manager and set new password. The invitation email contained an email link in this format: http://localhost:3000/account/enroll/TOKEN which is correct.
Prerequisites
Issue Description
The email sent when you invite an admin user to your shop has a button. When you click that button, it doesn't bring you to a page to accept the invitation or explain how to register and accept.
Steps to Reproduce
Setup
<yourname>[email protected]
.Reproduce
<yourname>[email protected]
Possible Solution
Need to figure out what should happen or what previously happened when this worked, and then make it happen again.
Versions
2.0.0 RC 11
The text was updated successfully, but these errors were encountered: