You've already forked snikket-web-portal
f363ff0b38
Previously, some kinds of errors would throw nice and fun cascades of exceptions. We now have a nice, clean error page for 500 and 503 (backend connectivity) errors which includes minimal debugging information for productive setups and a traceback for development setups. In any case, the full exception is logged to the log with an error ID which is printed on the error page.
7 lines
315 B
HTML
7 lines
315 B
HTML
{% extends "exception.html" %}
|
|
{% block box -%}
|
|
<header>{% trans %}Internal error{% endtrans %}</header>
|
|
<p>{% trans %}The web portal was not able to communicate with the backend.{% endtrans %}</p>
|
|
<p>{% trans %}Please try again later and/or inform your Snikket instance admin.{% endtrans %}</p>
|
|
{%- endblock %}
|