Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.6.4

Request #6651 Add clarification for custom login functions
Submitted: 2006-02-01 06:19 UTC
From: oscar at oscarm dot org Assigned: aashley
Status: Closed Package: Auth
PHP Version: Irrelevant OS:
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 44 - 4 = ?

 
 [2006-02-01 06:19 UTC] oscar at oscarm dot org
Description: ------------ It'd be helpful if the introduction to PEAR_Auth's example mentioned that the custom login function is called with 3 parameters: the username, the status of the authentication, and the authentication object itself. It took me a little while to figure this out (had to look in the code) so that I could test the authentication status and provide user's feedback on failed logins.

Comments

 [2006-03-20 21:28 UTC] arnaud (Arnaud Limbourg)
Could you be a bit more specific ? (location in the doc, code that needs to be modified) Thank you,
 [2006-06-29 22:45 UTC] glen dot davis at gmail dot com (Glen)
I believe he is referring to function loginFunction in Example 28-2 at http://pear.php.net/manual/en/package.authentication.auth.intro.php It would be helpful if it read: //takes three arguments: last attempted username, the authorization status, and the Auth object. //We won't use them in this simple demonstration--but you can use them to do neat things. function loginFunction($username='',$status=null,$auth=null) instead of the current function loginFunction()
 [2006-12-21 05:15 UTC] aashley at php dot net (Adam Ashley)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.