You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of a set of questions that arose during an internal code review.
When an error occurs, such as one of the Solr back-ends being unavailable, a response is given that is generic and unhelpful.
All error pages should be themed as normal.
Also, ideally, the codebase should have a development mode where stack traces are reported through the UI, and a production mode where the stack traces are collapsed/hidden and a user-friendly message is returned. The production mode should also email errors to a configurable email account.
The text was updated successfully, but these errors were encountered:
One of a set of questions that arose during an internal code review.
When an error occurs, such as one of the Solr back-ends being unavailable, a response is given that is generic and unhelpful.
All error pages should be themed as normal.
Also, ideally, the codebase should have a
development
mode where stack traces are reported through the UI, and aproduction
mode where the stack traces are collapsed/hidden and a user-friendly message is returned. Theproduction
mode should also email errors to a configurable email account.The text was updated successfully, but these errors were encountered: