PHP Fatal Errors

Permalink
I've been handed a site that uses Concrete5. Not overly familiar with it myself, but I am familiar with MVC structures and programming in PHP in general.

I've just recently been seeing these errors popping up in my error_log file and was hoping that somebody could point me to a quick solution.

[13-Nov-2012 16:24:12] PHP Warning:  require_once(Zend/Validate/Db/Abstract.php) [<a href='function.require-once'>function.require-once</a>]: failed to open stream: No such file or directory in .../concrete/libraries/3rdparty/Zend/Validate/Db/NoRecordExists.php on line 25
[13-Nov-2012 16:24:12] PHP Fatal error:  require_once() [<a href='function.require'>function.require</a>]: Failed opening required 'Zend/Validate/Db/Abstract.php' (include_path='.:/usr/lib64/php:/usr/lib/php:/usr/share/pear') in .../concrete/libraries/3rdparty/Zend/Validate/Db/NoRecordExists.php on line 25


AND

[13-Nov-2012 01:52:53] PHP Warning:  require_once(Zend/Http/UserAgent/Exception.php) [<a href='function.require-once'>function.require-once</a>]: failed to open stream: No such file or directory in .../concrete/libraries/3rdparty/Zend/Http/UserAgent/Features/Exception.php on line 25
[13-Nov-2012 01:52:53] PHP Fatal error:  require_once() [<a href='function.require'>function.require</a>]: Failed opening required 'Zend/Http/UserAgent/Exception.php' (include_path='.:/usr/lib64/php:/usr/lib/php:/usr/share/pear') in .../concrete/libraries/3rdparty/Zend/Http/UserAgent/Features/Exception.php on line 25


Now obviously a file seems to be not existing in the necessary location, but these errors only just started cropping up with no apparent reason. I've not done anything with the site since being handed it, no updates have been done, nothing. Errors just started showing up and I am uncertain as to why Concrete5 seems to be requesting a file that doesn't exist.

Any light somebody could shed on this would be much appreciated.

Thanks.

 
Qjohns replied on at Permalink Reply
Update:

I've found that the files seemed to have long require_once() paths, so I've changed the string that was calling the files. We'll see if that cures the problem... though it'll probably just cause the same if not another error.