@@ -21,10 +21,12 @@ Disabling the Bootstrap File and Class Caching
21
21
22
22
And to make the production environment as fast as possible, Symfony creates
23
23
big PHP files in your cache containing the aggregation of PHP classes your
24
- project needs for every request. However, this behavior can confuse your IDE
25
- or your debugger. This recipe shows you how you can tweak this caching
26
- mechanism to make it friendlier when you need to debug code that involves
27
- Symfony classes.
24
+ project needs for every request. However, this behavior can confuse your debugger,
25
+ because the same class can be located in two different places: the original class
26
+ file and the big file which aggregates lots of classes.
27
+
28
+ This recipe shows you how you can tweak this caching mechanism to make it friendlier
29
+ when you need to debug code that involves Symfony classes.
28
30
29
31
The ``app_dev.php `` front controller reads as follows by default::
30
32
@@ -38,8 +40,8 @@ The ``app_dev.php`` front controller reads as follows by default::
38
40
$request = Request::createFromGlobals();
39
41
// ...
40
42
41
- To make your debugger happier, disable all PHP class caches by removing (or
42
- commenting) the call to ``loadClassCache() ``::
43
+ To make your debugger happier, disable the loading of all PHP class caches
44
+ by removing the call to ``loadClassCache() ``::
43
45
44
46
// ...
45
47
@@ -56,7 +58,5 @@ commenting) the call to ``loadClassCache()``::
56
58
session.
57
59
58
60
Some IDEs do not like the fact that some classes are stored in different
59
- locations. To avoid problems, you can either tell your IDE to ignore the PHP
60
- cache files, or you can change the extension used by Symfony for these files::
61
-
62
- $kernel->loadClassCache('classes', '.php.cache');
61
+ locations. To avoid problems, you can tell your IDE to ignore the PHP cache
62
+ file.
0 commit comments