-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
forced password reset #232
Comments
Not sure if I meant this originally, but I see this as being a pretty simple process
|
I'd like to break this up into smaller pieces:
Marking it |
@jywarren Hi I've been looking around issues trying to find something I can take part in. Is this issue still live? I think I generally understand the task and what to do. If it's still something that needs to get done I'd be super excited to give it a go! |
Yes, this would be great -- thank you, we'd love your help!
Take a look at the admin_controller to see the functions we have now. I
think this is a remix of password reset key and password gibberish-izing as
should be reflected in that controller -- thanks!!!
…On Thu, Dec 7, 2017 at 9:14 AM, KevinKawai ***@***.***> wrote:
@jywarren <https://github.com/jywarren> Hi I've been looking around
issues trying to find something I can take part in. Is this issue still
live? I think I generally understand the task and what to do. If it's still
something that needs to get done I'd be super excited to give it a go!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#232 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ0gdScGlGDnfqgvkihOOSVqOypKLks5s9_LcgaJpZM4DjpZT>
.
|
@jywarren alrighty sounds great! I'll take a crack at it over the weekend and let you know if I run into any trouble. |
Super. Thanks!
…On Dec 7, 2017 7:55 PM, "KevinKawai" ***@***.***> wrote:
@jywarren <https://github.com/jywarren> alrighty sounds great! I'll take
a crack at it over the weekend and let you know if I run into any trouble.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#232 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ92McLuBzoDAh23xMLSFs1ZfKeFYks5s-IjxgaJpZM4DjpZT>
.
|
@jywarren Hey I was able to get some time to work on this issue and created a PR #1834. It's incomplete and still a work in progress. I had a bit of trouble with routes not working on my local machine so I had to change them but they are probably correct the way they are so I will change them back. If you have the chance to look through this and tell me if I'm on the right track that would be great. Thanks in advance! |
Oh oops, this is now done! |
@btbonval sez:
The text was updated successfully, but these errors were encountered: