Skip to content
New issue

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

Improve error handling #7

Open
anjackson opened this issue Jul 17, 2017 · 1 comment
Open

Improve error handling #7

anjackson opened this issue Jul 17, 2017 · 1 comment

Comments

@anjackson
Copy link
Contributor

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.

@anjackson anjackson added this to the 1.2.0 Feature Release milestone May 22, 2018
@anjackson
Copy link
Contributor Author

anjackson commented May 22, 2018

We should deal or kill this in the next release. Changing the Solr back-end may have helped resolve things.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant