Timeline for How to understand verbose log of Drupal to isolate a culprit function or template?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 4 at 7:21 | history | edited | 4uk4 | CC BY-SA 4.0 |
add debugging without Xdebug
|
| Jun 4 at 1:37 | comment | added | tostinni | Thks for the command, but it seems there was another error also, so this hand't helped us. I guess we'll try to set up Xdebug to avoid losing time on trivial error like this one. | |
| Jun 2 at 9:29 | history | edited | 4uk4 | CC BY-SA 4.0 |
added 387 characters in body
|
| Jun 2 at 6:58 | comment | added | 4uk4 |
They are compiled on demand and then stored. You can force that with drush twig-compile. If nothing is stored you have disabled that in your local dev settings. But if this is local debugging then you can use Xdebug where it stops at the original exception with the full template name and line number.
|
|
| Jun 2 at 2:55 | comment | added | tostinni |
I initially hadn't this folder, I removed settings.local.php and sites/default/files/php has been created but it's empty, so I'm not sure where those templates are stored then... Am I missing something in my setup that prevent this cache from being generated ?
|
|
| Jun 1 at 21:01 | history | answered | 4uk4 | CC BY-SA 4.0 |