Skip to content

Unable to reset password following a forgotten password request #581

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

Closed
gazzastone opened this issue Apr 9, 2015 · 15 comments
Closed

Unable to reset password following a forgotten password request #581

gazzastone opened this issue Apr 9, 2015 · 15 comments
Assignees
Milestone

Comments

@gazzastone
Copy link

Version
1.3.9

Steps To reproduce
Click on forgotten password email link and complete Reset Password dialog.

Expected Result
Expect password to be changed.

Actual result
ErrorException thrown with message "strtotime() expects parameter 1 to be string, array given".

Stacktrace:

#25 ErrorException in C:\xampp\htdocs\learninglocker\vendor\laravel\framework\src\Illuminate\Auth\Reminders\DatabaseReminderRepository.php:109
@gazzastone gazzastone changed the title Unable to reset password following a forgotton password request Unable to reset password following a forgotten password request Apr 9, 2015
@ryasmi ryasmi self-assigned this Apr 10, 2015
@ryasmi ryasmi added this to the 1.3.10 milestone Apr 10, 2015
@ryasmi
Copy link
Member

ryasmi commented Apr 10, 2015

@gazzastone this is a good one. I'm literally clueless. It looks like you have managed to create a user without a created_at property which is out of our control.

@ryasmi
Copy link
Member

ryasmi commented Apr 10, 2015

Note to self:
https://github.com/jenssegers/Laravel-MongoDB#auth
mongodb/laravel-mongodb#37

Adding 'Jenssegers\Mongodb\Auth\PasswordResetServiceProvider' to app.php didn't help.

@ryasmi
Copy link
Member

ryasmi commented Apr 10, 2015

I can't reproduce the issue, but when I try to fix it everything breaks.

@gazzastone
Copy link
Author

ok I will delete this user then recreate it and then do a password reset to see if the issue has gone

@ryasmi
Copy link
Member

ryasmi commented Apr 10, 2015

Ok sounds good.

@gazzastone
Copy link
Author

so deleted user. registered user ok. requested password reset get the same error

@ryasmi
Copy link
Member

ryasmi commented Apr 10, 2015

No way! That's crazy, I'll see what I can find out. We're all pretty busy over here today, so it may have to wait a little while.

@gazzastone
Copy link
Author

ok no probs

@sanduhrs
Copy link
Contributor

Same issue here, created_at actually is an array at least in my setup at 00e3a01

created_at = {array}[3]
  date = "2015-04-22 13:11:06.000000"
  timezone_type = 3
  timezone = "UTC"

@sanduhrs
Copy link
Contributor

Using the instructions from #163 fixes the issue for me.
Should this be documented at http://docs.learninglocker.net/installation/ or is it a bug?

sanduhrs pushed a commit to sanduhrs/learninglocker that referenced this issue Apr 22, 2015
@gazzastone
Copy link
Author

I can confirm that #163 has fixed the issue for me many thanks @sanduhrs

@ryasmi
Copy link
Member

ryasmi commented Apr 22, 2015

Ohhhhhh I'm a complete idiot! My apologies guys! I was well aware of this, but incorrectly assumed you were using the local configs.

@sanduhrs I think what needs to be documented is that you should always use the local config or duplicate the local config and use your own. Using your own just requires you to change the "bootstrap/start.php" file a little.

@ryasmi
Copy link
Member

ryasmi commented Apr 22, 2015

This explains why I couldn't reproduce this issue. We can't add that service provider in a commit because it screws up our continuous integration. However, we could potentially change "bootstrap/start.php" so that it contains...

$env = Helpers::getEnvironment([
  'local' => [gethostname()]
], gethostname());

This would ensure that you always used the local config unless you changed this file, which seems ideal to me.

@gazzastone
Copy link
Author

sounds like a plan to me

@ryasmi
Copy link
Member

ryasmi commented Apr 22, 2015

This issue has now been fixed and the fix has been merged into the develop branch. This should be released with version 1.3.10. Thanks @gazzastone and @sanduhrs for all of your help here.

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

No branches or pull requests

3 participants