-
Notifications
You must be signed in to change notification settings - Fork 4.4k
🐛 Bug Report: CreateTeamMembership and providing an email to an anonymous user, calls them by the incorrect name #8825
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
Comments
Hello @stnguyen90 what's the status of this issue? I'd love to pick it up and work on. |
Thanks @Meldiron |
Can I take this up if no one is working on it? |
@asharan2buff I'm working on it atm. I'll be a making a PR soon |
@Kraftsman1 are you still working on it? |
Related community thread: https://discord.com/channels/564160730845151244/1327754291468832880 |
Hi, can you please locate me the code where the changes are expected, I am new to this repo. Will help a ton |
Here is the code that should be changed: appwrite/app/controllers/api/teams.php Line 635 in 7ecba8c
It should instead be $emailVariables = [
'owner' => $user->getAttribute('name'),
'direction' => $locale->getText('settings.direction'),
/* {{user}}, {{team}}, {{redirect}} and {{project}} are required in default and custom templates */
'user' => $name,
'team' => $team->getAttribute('name'),
'redirect' => $url,
'project' => $projectName
]; cc @stnguyen90 |
Fixed in the PR here - #9218 |
👟 Reproduction steps
👍 Expected behavior
It should greet the person the email has been sent to, not the person who invited them.
👎 Actual Behavior
In the image here, you can see that this was sent to my email address, and my name there was set as "Your Name" which is what I provided. Inviter was the name of the user that did the inviting, yet is greeted in the email. It then also states that Inviter did the inviting.
🎲 Appwrite version
Appwrite Cloud
💻 Operating system
Windows
🧱 Your Environment
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: