Re: Possible BC break in between Auth 1.3.0 and 1.3.1

On Sep 13, 2006, at 4:31, Adam Ashley wrote:

Okay I've looked closely at how $_SESSION['_authsession']['username'] is set and frankly I don't see how your code example worked all the way back to 1.2.0 (i couldnt be bothered looking further back). I'm unable to replicate it with the latest versions (1.3.2 and 1.4.0RC1). the username field is set in Auth::setAuth() upon successful completetion of the Auth::login() call. it is set when the session storage is first setup and then never touched after that. The username field is handled completely independant of the auth container in use. The setting of db_fields to * enables a hack that loads all fields from the database for the users record and attaches them to the Auth session. Sorry but I don't think I can help you.

Never mind the the code I showed you. It is an kludge because of some AJAX calls. However check these test scripts. Host is running Auth 1.3.2: http://www.appelsiini.net/~tuupola/test/auth_132_a.php http://www.appelsiini.net/~tuupola/test/auth_132_a.phps http://www.appelsiini.net/~tuupola/test/auth_132_a.txt With this one logging in with username: test password: test works with Auth 1.3.0. With Auth 1.3.2 it however fails. With 1.3.2 I need to add line $options['db_fields'] = '*'; to make it work. http://www.appelsiini.net/~tuupola/test/auth_132_b.php http://www.appelsiini.net/~tuupola/test/auth_132_b.phps http://www.appelsiini.net/~tuupola/test/auth_132_b.txt Tested with PHP 4.4.2 and PHP 5.1.4 -- Mika Tuupola http://www.appelsiini.net/~tuupola/