Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.32.0
Bug #15915 Search for developers - invalid pagination combo values
Submitted: 2009-02-18 22:48 UTC
From: farell Assigned: amir
Status: Closed Package: pearweb
PHP Version: 5.2.8 OS: Windows XP
Roadmaps: 1.18.0    
Subscription  


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 - 43 = ?

 
 [2009-02-18 22:48 UTC] farell (Laurent Laville)
Description: ------------ While I've search different PEAR members, I've discovered with surprised a third combo that was empty in most case. But if you give a criteria that return more than 10 values, you'll have a BIG surprise. Values of this (pagination) combobox is well named when you search for packages but not for developers. Test script: --------------- search for example: lav Expected result: ---------------- <select name="setPerPage" id="perPage"> <option value="10" selected="selected">10</option> <option value="20">20</option> ... or even <select name="setPerPage" id="perPage"> <option value="10" selected="selected">10 developers</option> <option value="20">20 developers</option> ... Actual result: -------------- <select name="setPerPage" id="perPage"> <option value="10" selected="selected">10 packages</option> <option value="20">20 packages</option> ...

Comments

 [2009-03-22 15:38 UTC] amir (Amir Mohammad Saied)
The following patch has been added/updated: Patch Name: 15915 URL: patch 15915
 [2009-03-22 21:11 UTC] dufuz (Helgi Þormar Þorbjörnsson)
-Status: Open +Status: Closed -Assigned To: +Assigned To: amir -Roadmap Versions: +Roadmap Versions: 1.18.0
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.