Repository navigation
[2.1] Improve error reporting when a loop is detected #7801
Description
Description
In our error functions, we have some pretty good loop detection, and even produce a backtrace when a loop is detected.
BUT...
We do not capture the actual error that caused the loop. We just display the backtrace:
Line 51 in 4d7fbd8
We need to display the actual db error message as well.
Knowing we are in a loop isn't anywhere near as helpful as knowing WHY we're in a loop...
We have seen a couple of these lately...
Additional information/references
Without the error, you're flying blind, as in these forum support requests:
https://www.simplemachines.org/community/index.php?topic=586471.0
https://www.simplemachines.org/community/index.php?topic=586373.0
Activity
sbulen commentedon Mar 31, 2025
Another, more recent one:
https://www.simplemachines.org/community/index.php?topic=591387.0
[-]Improve error reporting when a loop is detected[/-][+][2.1] Improve error reporting when a loop is detected[/+]jdarwood007 commentedon Oct 25, 2026
The problem here is we don't want to drop a bunch of what could be sensitive info. So only in a developer environment would we want to issue something like a debug backtrace.
We could attempt to write to the cachedir for something like
$cachedir . '/loop-crash.log'or similar.