Bug #11006 Updated: include_path in php.ini broken

ID: 11006 Updated by: cynic Reported By: reitsmac@denison.edu Old-Status: Open Status: Feedback Bug Type: *Configuration Issues Operating system: PHP Version: 4.0.5 Assigned To: Comments: Is there PEAR.php in /usr/local/lib/php/ ? You must include the directory that contains this file, so if /usr/local/lib/php/ contains pear/, you should make it set_ini( 'include_path' , '.:/usr/local/lib/php/pear' ) Previous Comments: --------------------------------------------------------------------------- [2001-05-23 15:02:56] reitsmac@denison.edu Yes. 755. Most includes are in the same directory. So with the broken include_path reading '.:/usr/local/lib/php' scripts cannot read config.inc but have no trouble with ./config.inc. --------------------------------------------------------------------------- [2001-05-23 14:44:57] cynic@php.net can you put echo ini_get( 'include_path' ) somewhere in that script? --------------------------------------------------------------------------- [2001-05-23 09:46:54] cynic@php.net Is there PEAR.php in /usr/local/lib/php/ ? You must include the directory that contains this file, so if /usr/local/lib/php/ contains pear/, you should make it set_ini( 'include_path' , '.:/usr/local/lib/php/pear' ) --------------------------------------------------------------------------- [2001-05-23 03:50:35] sniper@php.net Works for me just fine. Is that path readable by the user the Apache runs as? --Jani --------------------------------------------------------------------------- [2001-05-21 21:39:31] reitsmac@denison.edu Here's a link to a broken web server: http://charlie1.test.denison.edu/horde/test.php It's the Horde project test page to determine if the functionality is present necessary to support horde. At the bottom of the page note that PEAR is broken. Yet the phpinfo link at the top of the page shows the include_path is '.:/usr/local/lib/php'. I can fix the problem by removing include_path from php.ini and depending on the default path. --------------------------------------------------------------------------- The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online. ATTENTION! Do NOT reply to this email! To reply, use the web interface found at http://bugs.php.net/?id=11006&edit=2