Error Message after Installing 5.4.0.2
Permalink
I tried to upgrade to 5.4 but keep seeing this
error message:
Warning: require_once(Zend/Cache/Backend/File.php) [function.require-once]: failed to open stream: No such file or directory in /home/funnyins/public_html/concrete/libraries/3rdparty/Zend/Cache.php on line 132
Fatal error: require_once() [function.require]: Failed opening required 'Zend/Cache/Backend/File.php' (include_path='.:/usr/lib/php:/usr/local/lib/php:/home/funnyins/php') in /home/funnyins/public_html/concrete/libraries/3rdparty/Zend/Cache.php on line 132
I then decided to reinstall C5 by deleting all the core files on the webserver and upload the new files back to the server again. Still, I keep seeing the error message above.
Anyone have any idea how to resolve this problem?
error message:
Warning: require_once(Zend/Cache/Backend/File.php) [function.require-once]: failed to open stream: No such file or directory in /home/funnyins/public_html/concrete/libraries/3rdparty/Zend/Cache.php on line 132
Fatal error: require_once() [function.require]: Failed opening required 'Zend/Cache/Backend/File.php' (include_path='.:/usr/lib/php:/usr/local/lib/php:/home/funnyins/php') in /home/funnyins/public_html/concrete/libraries/3rdparty/Zend/Cache.php on line 132
I then decided to reinstall C5 by deleting all the core files on the webserver and upload the new files back to the server again. Still, I keep seeing the error message above.
Anyone have any idea how to resolve this problem?
I got the same error too when installing 5.4.0.3. Is it a problem on my webhost's side?
You can see that something is not pointing to the right location. It lists the include path as
.:/usr/lib/php:/usr/local/lib/php:/home/funnyins/php
However, the file it is trying to load is in
/home/funnyins/public_html/concrete/libraries/3rdparty
The directory above is nowhere in the include path. As a result, it will never find File.php. The include path is set in <root>/concrete/config/base.php. If the include path is not being set correctly, then base.php is not being executed, or a problem of some kind is preventing the include path from being updated.
You should check the web server error logs to see if there is any more information about the installation. It could be something simple, such as the permissions on the files or directories prevents the web server from reading (or writing) them. Directory permissions are discussed here.
http://www.concrete5.org/documentation/installation/file-directory-...
You should clear everything in files/cache and in files/cache_objects, if it exists. Make sure you clear your browser cache before doing the upgrade.
You don't say what version you are upgrading from. It is possible that there are specific upgrade instructions when upgrading from a particular version before 5.4.0.
.:/usr/lib/php:/usr/local/lib/php:/home/funnyins/php
However, the file it is trying to load is in
/home/funnyins/public_html/concrete/libraries/3rdparty
The directory above is nowhere in the include path. As a result, it will never find File.php. The include path is set in <root>/concrete/config/base.php. If the include path is not being set correctly, then base.php is not being executed, or a problem of some kind is preventing the include path from being updated.
You should check the web server error logs to see if there is any more information about the installation. It could be something simple, such as the permissions on the files or directories prevents the web server from reading (or writing) them. Directory permissions are discussed here.
http://www.concrete5.org/documentation/installation/file-directory-...
You should clear everything in files/cache and in files/cache_objects, if it exists. Make sure you clear your browser cache before doing the upgrade.
You don't say what version you are upgrading from. It is possible that there are specific upgrade instructions when upgrading from a particular version before 5.4.0.
Hi Mose,
Thank you very much for your reply.
The error is indeed a permission issue on my webhost's server and they have got it fixed.
Thank you very much for your reply.
The error is indeed a permission issue on my webhost's server and they have got it fixed.
