metadata: Error in Symfony2's production environment (only) caused with version >= 1.4.0
After an upgrade from 1.3.0 to 1.4.0 (or 1.4.1, tried both), the exception added in this commit https://github.com/schmittjoh/metadata/commit/f68e2a8b5ddee789a5eef533f4f79e3baddb81e8 is thrown whenever I access one of the pages of my website (but not all of them). It happens only with app.php (not app_dev.php / app_test.php).
Here’s the stacktrace :
[2013-09-03 14:59:50] request.CRITICAL: Uncaught PHP Exception LogicException: "The cache must return instances of ClassMetadata, but got false." at /var/www/xxx/vendor/jms/metadata/src/Metadata/MetadataFactory.php line 81 {"exception":"[object] (LogicException: The cache must return instances of ClassMetadata, but got false. at /var/www/xxx/vendor/jms/metadata/src/Metadata/MetadataFactory.php:81)"} []
I’ve reverted the library to 1.3.0 temporarily, but would very much like to see this resolved. Thanks for your help.
About this issue
- Original URL
- State: closed
- Created 11 years ago
- Comments: 15 (9 by maintainers)
Commits related to this issue
- Set cache files to be world readable Fixes #32 — committed to tommygnr/metadata by tommygnr 11 years ago
@schmittjoh I don’t think there was a PHP error, as it worked fine in Symfony’s dev environment (app_dev.php). I’ll try to change app.php to add the debug flag. @stof I’ve
rm -rf app/cache/*between the updates, so it should not be an issue.