We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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:
SMF/Sources/Errors.php
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...
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
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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:
SMF/Sources/Errors.php
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
The text was updated successfully, but these errors were encountered: