You've already forked snikket-web-portal
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.
10 lines
362 B
HTML
10 lines
362 B
HTML
{% extends "unauth.html" %}
|
|
{% from "library.j2" import avatar with context %}
|
|
{% block head_lead %}
|
|
<title>{% trans %}Snikket Web Portal{% endtrans %}</title>
|
|
{% endblock %}
|
|
{% block topbar_right %}
|
|
{{- super() -}}
|
|
<nav class="usermenu">{{ user_info.display_name }}{% call avatar(user_info.address, user_info.avatar_hash ) %}{% endcall %}</nav>
|
|
{%- endblock %}
|