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

Bug #16087 Failed opening required 'PEAR/Remote.php'
Submitted: 2009-04-11 04:55 UTC
From: bbrunekreeft Assigned: saltybeagle
Status: Closed Package: PEAR_Frontend_Web (version 0.7.3)
PHP Version: 5.2.3 OS: Linux
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 : 9 - 6 = ?

 
 [2009-04-11 04:55 UTC] bbrunekreeft (Bert Brunekreeft)
Description: ------------ Right after an upgrade from PEAR-1.7.3 to the new PEAR-1.8.0, the following message appears into the apache log files: PHP Fatal error: require_once() [<a href='function.require'>function.require</a>]: Failed opening required 'PEAR/Remote.php' (include_path='/path/to/PEAR') in /path/to/PEAR/PEAR/Frontend/Web.php on line 35 Test script: --------------- Using Pear via Pear_Frontend_Web Expected result: ---------------- See the Pear_Frontend_Web interface Actual result: -------------- blank page and error message in log file

Comments

 [2009-04-11 04:59 UTC] bbrunekreeft (Bert Brunekreeft)
Correction: pear upgrade was from PEAR-1.7.2 to PEAR-1.8.0
 [2009-04-12 00:34 UTC] doconnor (Daniel O'Connor)
 [2009-04-15 10:06 UTC] saltybeagle (Brett Bieber)
-Status: Verified +Status: Closed -Assigned To: +Assigned To: saltybeagle
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. PEAR/Remote.php was removed in 5.8, and the PEAR_Remote class was not used directly within PEAR_Frontend_Web. By replacing the require_once statement with: require_once "PEAR.php"; require_once "PEAR/Config.php"; This should fix the error.