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

Bug #11199 "New search" does not select current package
Submitted: 2007-06-01 10:28 UTC
From: cweiske Assigned: cellog
Status: Closed Package: pearweb (version 1.15.2)
PHP Version: Irrelevant OS:
Roadmaps: 1.16.1    
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:
Solve the problem : 44 + 24 = ?

 [2007-06-01 10:28 UTC] cweiske (Christian Weiske)
Description: ------------ Clicking on "New search" already transmits the name of the currently selected package in the url, but this package name is not preselected in the search form.


 [2007-06-01 10:35 UTC] cweiske (Christian Weiske)
 [2007-06-01 10:38 UTC] wiesemann (Mark Wiesemann)
I had reported this already in Bug #10872. While it is marked as fixed in 1.15.0 and works on my local pearweb installation (CVS version), it doesn't work online (which should be version 1.15.2).
 [2007-06-02 20:22 UTC] wiesemann (Mark Wiesemann)
Short update: This still doesn't work in the released version 1.16.0.
 [2007-06-02 20:39 UTC] cweiske (Christian Weiske)
I didn't find your bug, sorry. I knew there was one for this request, but I just was too blind.
 [2007-06-09 21:50 UTC] dufuz (Helgi ├×ormar)
This is so odd, it works perfectly on my local machine and also on Davids local checkout, I'll look further into the matter
 [2007-06-11 04:49 UTC] cellog (Greg Beaver)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on by the end of next Sunday (CET). If this was a problem with the 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. turns out, register_globals is enabled on *everyone*'s dev box (legacy httpd.conf setting) but not on the live server, and we were using $package_name instead of $_GET['package_name'] fix is now committed and is also live thanks to a little sudo cp action on my part