From: Marc G. F. <sc...@hu...> - 2009-10-01 04:40:48
|
Chris, it appears that if you create a new user in the newest slashcode, that user can't login afterwards (I've tested it to make sure it wasn't something like user not being aware its case dependent) ... If I go into the DB and do an update using md5() to set the password, afterwards I can login fine, so I suspect something in the routing to create the password is failing ... ? Not sure how best to debug this one though ... ---- Marc G. Fournier Hub.Org Hosting Solutions S.A. sc...@hu... http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... |
From: Shane Z. <sh...@lo...> - 2009-10-01 15:50:53
|
On Oct 1, 2009, at 12:40 AM, Marc G. Fournier wrote: > > Chris, it appears that if you create a new user in the newest > slashcode, > that user can't login afterwards (I've tested it to make sure it > wasn't > something like user not being aware its case dependent) ... > > If I go into the DB and do an update using md5() to set the password, > afterwards I can login fine, so I suspect something in the routing to > create the password is failing ... ? > > Not sure how best to debug this one though ... So you have a clean install of slash, correct? If I recall correctly, when a new account is created it actually puts the autogenerated-password in the users.newpasswd field. Then, once the user has authenticated their email address, it removes users.newpasswd and users.passwd is used. So in this case, Slash::Test is probably your friend. If you've not used Slash::Test, do a "perldoc Slash::Test" on the command line. Because you could use it as such perl -MSlash::Test -e "print $slashdb->createUser('nicknamefoo','em...@lo... ','nicknamefoo');" and then follow along in the DB and check users.passwd, users.newpasswd and compare that with the autogenerated email's information contained within it. That should get you started. Shane |
From: Marc G. F. <sc...@hu...> - 2009-10-01 16:27:44
|
On Thu, 1 Oct 2009, Shane Zatezalo wrote: > > On Oct 1, 2009, at 12:40 AM, Marc G. Fournier wrote: > >> >> Chris, it appears that if you create a new user in the newest >> slashcode, >> that user can't login afterwards (I've tested it to make sure it >> wasn't >> something like user not being aware its case dependent) ... >> >> If I go into the DB and do an update using md5() to set the password, >> afterwards I can login fine, so I suspect something in the routing to >> create the password is failing ... ? >> >> Not sure how best to debug this one though ... > > So you have a clean install of slash, correct? Yes, totally starting from scratch on this one ... > If I recall correctly, when a new account is created it actually puts > the autogenerated-password in the users.newpasswd field. Then, once the > user has authenticated their email address, it removes users.newpasswd > and users.passwd is used. Maybe that is the problem: mysql> select passwd, newpasswd from users where uid = 10; +----------------------------------+-----------+ | passwd | newpasswd | +----------------------------------+-----------+ | bee39b164cdb00297d76d83b17cd6ef5 | NULL | +----------------------------------+-----------+ 1 row in set (0.00 sec) and ... mysql> select newpasswd from users; +-----------+ | newpasswd | +-----------+ | NULL | | | | NULL | | NULL | | NULL | | NULL | | NULL | | NULL | | NULL | | NULL | +-----------+ 10 rows in set (0.00 sec) doesn't look like the newpasswd field is ever being set ... ---- Marc G. Fournier Hub.Org Hosting Solutions S.A. sc...@hu... http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:sc...@hu... |