Timeline for Fatal error trace not shown in development setup
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 15, 2022 at 10:21 | answer | added | kontur | timeline score: 0 | |
| Nov 10, 2022 at 12:00 | comment | added | Tom J Nowell♦ |
then it seems you don't have a PHP error log, and are relying on the WP debug.log, which is suboptimal. It means anything that fails before the WP error handler is added is not logged or caught because content/debug.log has not been set yet. You also have the problem that if your error reporting level is weird it may not log certain types of error at all. Likewise if you use @ a lot, @ does not fix errors, it silences them, the error still happens. I don't think this is necessarily WP specific and you're shooting yourself in the foot by looking only in WP circles. It's generic PHP
|
|
| Nov 10, 2022 at 9:05 | comment | added | kontur |
@TomJNowell Thanks, I'm not trying to debug one specific issue, but generally the fact that I don't get traces for these. Often it's using a WP object as Array or other simple mistakes, but without the trace it can be quite a challenge to narrow them down. For $ php -i I get php -i | grep "log"` error_log => no value => no value and log_errors => On => On, viewing phpinfo() output in the project I have error_log pointing to the local /wp-content/debug.log file of that project.
|
|
| Nov 9, 2022 at 13:59 | comment | added | Tom J Nowell♦ |
be sure you're checking the PHP log and not the Apache/Nginx log, and that php.ini is configured to log to an error log. Also errors don't just randomly occur like this, they always have a cause and pattern, so narrowing it down further will be important
|
|
| Nov 9, 2022 at 13:29 | comment | added | kontur |
@TomJNowell Jep, it's a localhost setup for dev; no logs in my server/host specific log. And I do get e.g. array index offset warnings and other errors into debug.log — just the Fatal ones show up nowhere.
|
|
| Nov 9, 2022 at 13:12 | comment | added | Tom J Nowell♦ |
have you used a process of elimination to determine which theme/plugin/file it is that's causing it? Have you checked the server level error log rather than the WP specific one at wp-content/debug.log? Your host can point you towards it if you're not sure where that is
|
|
| Nov 9, 2022 at 12:48 | history | asked | kontur | CC BY-SA 4.0 |