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

Bug #8165 Error on code
Submitted: 2006-07-08 11:58 UTC
From: iwarner Assigned: farell
Status: Closed Package: PEAR_Info (version 1.6.1)
PHP Version: 5.1.2 OS: Windows XP
Roadmaps: 1.7.0RC1    
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 : 31 - 4 = ?

 
 [2006-07-08 11:58 UTC] iwarner (Ian Warner)
Description: ------------ Error on execute Fatal error: Call to a member function getVersion() on a non-object in C:\XAMPP\xampp\php\pear\PEAR\Info.php on line 57 Test script: --------------- either require_once 'PEAR/Info.php'; PEAR_Info::show(); or $info = new PEAR_Info(); $info->show(); both give me above error

Comments

 [2007-06-28 05:39 UTC] cweiske (Christian Weiske)
What do you get then var_dump()ing the $info object?
 [2007-06-29 21:03 UTC] farell (Laurent Laville)
Ian, With current CVS version (upcoming version 1.7.0), we still have this problem. But, to be honest, it should not be arrive. Why ? Because the pear config file "pear.ini" (on windows) ".pearrc" (on other platform) should exists into PEAR_CONFIG_SYSCONFDIR directory (defined by constant). If it's not, second parameter of PEAR_Info class constructor (in version 1.7.0) will allow to define where to find this file. Interresting for non standard PEAR installation, or if you don't want to have a such config file outside your PEAR environment. Are you agree with such situation. If YES, I will close the bug !
 [2007-06-30 16:57 UTC] farell (Laurent Laville)
*** assigned to me and fixed on upcoming release 1.7.0RC1. Will raise a warning message if pear config file does not exist to prevent unexpected results.
 [2007-06-30 16:58 UTC] farell (Laurent Laville)
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.