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

Bug #2446 english errors in DB container
Submitted: 2004-10-04 14:46 UTC Modified: 2006-01-08 07:42 UTC
From: quipo Assigned: lsmith
Status: Closed Package: Auth
PHP Version: Irrelevant OS:
Roadmaps: (Not assigned)    
Subscription  


 [2004-10-04 14:46 UTC] quipo
Description: ------------ Typos: Responce => Response Authenthication => Authentication See patch below. Reproduce code: --------------- 213c213 < * challenge response password authenthication --- > * challenge response password authentication 216c216 < function fetchData($username, $password, $isChallengeResponce=false) --- > function fetchData($username, $password, $isChallengeResponse=false) 218c218 < //print "Container_DB::fetchData($username, $password, $isChallengeResponce) <br/>\n"; --- > //print "Container_DB::fetchData($username, $password, $isChallengeResponse) <br/>\n"; 232,234c232,234 < /** < Old Style, removed to go around the oci8 < problem --- > /* > Old Style, removed to go around the oci8 > problem 237c237 < --- > 246c246 < --- > 250c250 < --- > 262c262 < --- > 266,267c266,267 < // If using Challenge Responce md5 the pass with the secret < if ($isChallengeResponce) { --- > // If using Challenge Response md5 the pass with the secret > if ($isChallengeResponse) { 295,299c295,299 < * Returns a list of users from the container < * < * @return mixed < * @access public < */ --- > * Returns a list of users from the container > * > * @return mixed > * @access public > */ 352c352 < --- > 424c424 < --- > 445,451c445,451 < * Determine if this container supports < * password authenthication with challenge responce < * < * @return bool < * @access public < */ < function supportsChallengeResponce() --- > * Determine if this container supports > * password authentication with challenge response > * > * @return bool > * @access public > */ > function supportsChallengeResponse() 455c455 < --- > 463c463 < --- >

Comments

 [2006-01-08 07:42 UTC] lsmith
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.