Timeline for How to understand verbose log of Drupal to isolate a culprit function or template?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 8 at 6:35 | comment | added | 4uk4 | That would be interesting to step through the code with Xdebug to discover why the debugging method without Xdebug doesn't work. | |
| Jun 8 at 4:22 | comment | added | tostinni | Thank you for the suggestion, but on our project it doesn't seem to make any change, that's quite weird :/ | |
| Jun 4 at 7:22 | comment | added | 4uk4 | OK, I wondered why Xdebug shows the Twig error and the Drupal logs don't. I've found the line responsible. So without Xdebug you could temporarily remove this line and get the template name and line number. See the edited answer. | |
| Jun 4 at 1:35 | vote | accept | tostinni | ||
| Jun 4 at 1:35 | history | answered | tostinni | CC BY-SA 4.0 |