Warning: You are browsing the documentation for version 2.6 which is not maintained anymore.
If some of your projects are still using this version, consider upgrading.
When you work on a Symfony project on your local machine, you should use the
dev environment (
app_dev.php front controller). This environment
configuration is optimized for two main purposes:
- Give the developer accurate feedback whenever something goes wrong (web debug toolbar, nice exception pages, profiler, ...);
- Be as similar as possible as the production environment to avoid problems when deploying the project.
And to make the production environment as fast as possible, Symfony creates big PHP files in your cache containing the aggregation of PHP classes your project needs for every request. However, this behavior can confuse your IDE or your debugger. This recipe shows you how you can tweak this caching mechanism to make it friendlier when you need to debug code that involves Symfony classes.
app_dev.php front controller reads as follows by default:
1 2 3 4 5 6 7 8
// ... $loader = require_once __DIR__.'/../app/bootstrap.php.cache'; require_once __DIR__.'/../app/AppKernel.php'; $kernel = new AppKernel('dev', true); $kernel->loadClassCache(); $request = Request::createFromGlobals();
To make your debugger happier, disable all PHP class caches by removing the
loadClassCache() and by replacing the require statements like
1 2 3 4 5 6 7 8 9
// ... // $loader = require_once __DIR__.'/../app/bootstrap.php.cache'; $loader = require_once __DIR__.'/../app/autoload.php'; require_once __DIR__.'/../app/AppKernel.php'; $kernel = new AppKernel('dev', true); // $kernel->loadClassCache(); $request = Request::createFromGlobals();
If you disable the PHP caches, don't forget to revert after your debugging session.
Some IDEs do not like the fact that some classes are stored in different locations. To avoid problems, you can either tell your IDE to ignore the PHP cache files, or you can change the extension used by Symfony for these files: