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

Bug #15730 Roadmap -> Show Feature Detail displays oddly
Submitted: 2009-01-22 15:51 UTC Modified: 2009-01-22 17:34 UTC
From: doconnor Assigned: dufuz
Status: Closed Package: pearweb (version CVS)
PHP Version: 5.2.6 OS:
Roadmaps: 1.18.0    
Subscription  


 [2009-01-22 15:51 UTC] doconnor (Daniel O'Connor)
Description: ------------ While I would like to compare current site pear.php.net with euk1.php.net about package roadmap handle, I've noticed : On euk1.php.net, and package QF2 for example, when you click from page [1] on link "Show Old Roadmaps", you go to [2] Click either on 0.1.0 or 0.2.0 "Show Feature Detail" link I found strange to see something like Showing 1-7 of 2 or Showing 1-3 of 1 Is someone can explain me, or is it just a display bug ? Test script: --------------- View http://euk1.php.net/bugs/roadmap.php?roadmapdetail=0.2.0&package=HTML_QuickForm2&showold=1#a0.2.0 Expected result: ---------------- "1-7 of 7" Actual result: -------------- "1-7 of 2" Looks like a pager refactoring attack?

Comments

 [2009-01-22 16:15 UTC] doconnor (Daniel O'Connor)
Looks like roadmap.php Line 467: $rows = $features->find(false); $total_rows = $dbh->getOne('SELECT FOUND_ROWS()'); Some kind of sneaky extra query is slipping in there.
 [2009-01-22 16:31 UTC] doconnor (Daniel O'Connor)
DB_DataObject ($features->find(false)) should just return the number of rows found, shouldn't it? $features = clone($bugdb); $bugs = clone($bugdb); $roadmaps->roadmap_id = $allroadmaps->id; $features->selectAs(); $features->joinAdd($roadmaps); $features->bug_type = 'Feature/Change Request'; $rows = $features->find(false); $total_rows = $dbh->getOne('SELECT FOUND_ROWS()'); ... so $total_rows is pointless?
 [2009-01-22 17:34 UTC] dufuz (Helgi Þormar Þorbjörnsson)
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.