-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Error sending password reset email when not using confirmable (reopened #124) #321
Comments
I am having the same problem, despite #124 said it was solved. Below is my error message. I am however using v0.1.31, different then @fertingoff
|
@dshcheung actually I was using v0.1.31 (last stable through bundle update) but without results. Later I noted that @qx in #124 initially reported the same problem, but then he wrote, literally "'0.1.32 fixed'". So I found the last version of v0.1.32 and did my best. Eventually I still have the same unsuccessful result. |
Please try testing this against master @fertingoff |
I've just published and pushed 0.1.32 for devise_token_auth as well as 0.0.27 for ng-token-auth (if you happen to be using that as the client). Please close this issue if fixed in the latest versions. |
@booleanbetrayal, thank you so much for your quick response. The error is gone with v0.1.32. But I'm facing the same problem, described by @dshcheung... Would appreciate any hints. |
@booleanbetrayal @fertingoff |
Great! @fertingoff - could you ensure that any custom overrides aren't interfering, like @dshcheung was experiencing? |
@booleanbetrayal passwords_controller.rb#edit form a link for email on a line 112:
The link looks like that for me in incoming email(note, that I found, that this twist is made by line 234 in models/devise_token_auth/concerns/user.rb#generate_url:
Would appreciate any help or ideas. I'm using devise_token_auth v0.1.32. and ng-token-auth v0.0.27. Thanks! |
Hi @fertingoff - I'm a bit confused by the URL you posted. It appears to be invalid (two protocol delimiters - The fragment portion in |
Hi @booleanbetrayal
Here is what I have in logs (pay attention to line number 4):
Yeah, it looks weird but at least it works with correct link, crated manually: Please note, that I changed nothing in gem codebase, so I still have no idea why I have two protocol delimiters. |
So, @booleanbetrayal what do you think, should I try to change a code of this version or it's worth to wait for possible update on this issue? thx! |
The problem was that we were trying to use custom routes for resetting password and it made some conflicts. There is no need to do that. Everything works automatically. |
Folks, after closing #124 I still have the problem.
I'm using v0.1.32.beta9 (the most recent version as far as I see).
Any ideas? Thanks!
The text was updated successfully, but these errors were encountered: