upgraded symfony and failed in sfCoreAutoload

by prettyscripts on 2010-05-28 13:59:12

frameworksymfony

one of the development projects was upgraded from symfony V142 to the latest V144. my convention for the development is to symbolic link the symfony core files under lib/vendor directory.

after the upgrade, the browser displayed blank page with the following error logged:

PHP Warning: sfCoreAutoload::require(/config/sfProjectConfiguration.class.php) [sfcoreautoload.require]: failed to open stream: No such file or directory in /path/to/symfony-1.4.4/lib/autoload/sfCoreAutoload.class.php on line 99

running from command line initially had this warning but the problem went away after cache was cleared. however accessing from the browser continues to have problem.

it's not the first time i upgraded a project to the latest symfony but it's the first time this happens.

after some research, it was mentioned that application runs normally after restarting apache. yes, it works!  if you know why, please leave a comment.

development environment: fedora core 10, apache 2.2.10, php 5.2.6, mysql 5.0.67.

updated: it seems this only happens when upgrading to V144?

Tags: apache, autoload, symfony

No feedback yet

Leave a comment


Your email address will not be revealed on this site.
PoorExcellent
note: all comments are moderated. do not spam and do not advertise. only comments relevant to the post will be published.
(Line breaks become <br />)
(For my next comment on this site)
(Allow users to contact me through a message form -- Your email will not be revealed!)