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

Reset password comes as a Mandrillapp tracking link with wrong path #112

Closed
username1290 opened this issue Oct 4, 2017 · 3 comments
Closed

Comments

@username1290
Copy link

username1290 commented Oct 4, 2017

- Do you want to request a feature or report a bug?
Bug

- What is the current behavior?
Reset password link is a Mandrill link, which in turn makes the reset password unsuccessful.
After tracking the link, the redirected path is wrong: example.com/#recovery_token=somenumbers
missing admin from the path.

- If the current behavior is a bug, please provide the steps to reproduce.
1.- create a netlifycms instance
2.- change to a theme that uses the simple Netlify Identity login (not the git identity)
3.- Create a user inside app.netlify.com
4.- Send password reset

- What is the expected behavior?
Link is a reset password

- Please mention your Go version, and operating system version.
OSX Sierra,
Go version unknown (command not found)

@username1290 username1290 changed the title Reset password comes inside Mandrillapp link Reset password comes as a Mandrillapp tracking link Oct 4, 2017
@username1290 username1290 changed the title Reset password comes as a Mandrillapp tracking link Reset password comes as a Mandrillapp tracking link with wrong path Oct 4, 2017
@brycekahle
Copy link
Contributor

The email paths are currently set to use the root of the site. We need to expose those configuration settings in the UI to fix this issue.

@tranphuoctien
Copy link

It's just API and it's get path of router to send for user. This make wrong path reset password. We should add endpoint redirect when user click to this.

@alexeychikk
Copy link

I still have the issue. Is this fix released?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants