Feature #15322
Updated by Jim Pingle about 2 months ago
If After fixing #15263 if there is a PHP error early enough in the output of a page it ends up returning a 500 error with a blank page. We should handle this better if possible. The ideal case would redirect to the crash reporter but if PHP itself has a problem that could end up in a loop or similar bad scenario. It seems like the best path is to return a static page that contains a link to the crash reporter along with some other helpful information. It wouldn't need to be much, could be similar to the login screen, a page with the logo and a short message explaining there was a problem. Adding a 50x error the 500 page to the nginx config is easy but we may also have to change fastcgi error interception. This isn't a blocker but nice to have, can be moved forward if there is no time. If it's easy enough, once we have a basic appropriate static page we could use it for 404 errors as well.