Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.9.3
Bug #4521 Pager get's wrong value if there is no row limit
Submitted: 2005-06-03 18:17 UTC
From: wiesemann Assigned: asnagy
Status: Closed Package: Structures_DataGrid
PHP Version: Irrelevant OS: Irrelevant
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 : 30 - 17 = ?

 
 [2005-06-03 18:17 UTC] wiesemann
Description: ------------ When using HTMLTable renderer without a row limit, Pager get's null value for "perPage" option which is then resetted (because of null value) to Pager's default value for this option (10). The following change fixes the problem: change line 523 (curr. CVS): 'perPage' => $this->_dg->rowLimit, to: 'perPage' => is_null($this->_dg->rowLimit) ? $count : $this->_dg->rowLimit,

Comments

 [2005-06-06 21:16 UTC] asnagy
This bug has been fixed in CVS. In case this was a documentation problem, the fix will show up at the end of next Sunday (CET) on pear.php.net. In case this was a pear.php.net website problem, the change will show up on the website in short time. Thank you for the report, and for helping us make PEAR better.