No that does not exist. When I copy PEAR.php into the vufind\web folder I then get the following error
Warning: include_once(PEAR5.php) [function.include-once]: failed to open stream:
No such file or directory in C:\VuFind\web\PEAR.php on line
Warning: include_once() [function.include]: Failed opening 'PEAR5.php' for inclusion (include_path='.;C:\php5\pear') in C:\VuFind\web\PEAR.php on line 730
Warning: require_once(Smarty/Smarty.class.php) [function.require-once]: failed to open stream: No such file or directory in C:\VuFind\web\sys\Interface.php on line 28
Fatal error: require_once() [function.require]: Failed opening required 'Smarty/Smarty.class.php' (include_path='.;C:\php5\pear') in C:\VuFind\web\sys\Interface.php on line 28
From: Demian Katz [mailto:firstname.lastname@example.org]
Sent: Friday, 2 August 2013 10:20 PM
To: Byron Smith; email@example.com
Subject: RE: [VuFind-Tech] pear error
Does c:\php5\pear\PEAR.php exist? What happens if you copy PEAR.php into c:\VuFind\web temporarily?
Byron Smith [firstname.lastname@example.org]
Sent: Friday, August 02, 2013 8:12 AM
Subject: [VuFind-Tech] pear error
I am installing Vufind for yet another library here in Australia. I have run into a hurdle with PHP/Pear. I am getting the following message when opening Vufind in a web browser.
Warning: require_once(PEAR.php) [function.require-once]: failed to open stream: No such file or directory in C:\VuFind\web\index.php on line 43
Fatal error: require_once() [function.require]: Failed opening required 'PEAR.php' (include_path='.;C:\php5\pear') in C:\VuFind\web\index.php on line 43
The pear install itself went without a hitch and I have made sure that the ‘include_path’ in the php.ini file is pointing to the correct path for pear and have verified that the pear modules are installed correctly. I am really confused as to why it is even referencing ‘c:\php5\pear’ since this is not referenced anywhere in the php.ini or anywhere else that I can see.
The server that this is installed on does have a number of applications running on it however I have double checked to make sure there are no other instances of php.ini. Does anyone have any advice on how I could trouble shoot this issue?