- 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
Can you recall what the WSOD error was - can you provide a stack trace.
Was it a timeout, an out of memory, or something else?
We have our db log set to maximum 1000000 to keep the history from /admin/config/development/logging. But my guess is that this causes the Top 'page not found' errors not to work, as there are too many results to group by on.
Drupal should first check what is the setting value of "Database log messages to keep" in /admin/config/development/logging. After that it could probably either check whats the actual count of logs in the db or already decide by the setting that it shouldn't try to group by on all of the logs in the db (haven't actually checked the code, maybe i am wrong on this assumption).
As the db log setting is available in core, then the top 404 errors functionality should be able to play nice with it. So in my eyes some sort of limiting would be good on the 404 error report, to make this necessary functionality work for us.
Postponed: needs info
11.0 🔥
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Can you recall what the WSOD error was - can you provide a stack trace.
Was it a timeout, an out of memory, or something else?