mirror of
https://github.com/zulip/zulip.git
synced 2025-10-23 04:52:12 +00:00
c1857b2c86
Depending on the kind of config error being shown, different "go back" links may be more appropriate. We probably hard-coded /login/ for it, because these config errors are most commonly used for authentication backend config error, where it makes sense to have /login/ as "go back", because the user most likely indeed got there from the login page. However, for remote_billing_bouncer_not_configured, it doesn't make sense, because the user almost surely is already logged in and got there by clicking "Plan management" inside the gear menu in the logged in app.
33 lines
963 B
HTML
33 lines
963 B
HTML
{% extends "zerver/portico.html" %}
|
|
|
|
{% block title %}
|
|
<title>{{ _("Configuration error") }} | Zulip</title>
|
|
{% endblock %}
|
|
|
|
{% block portico_content %}
|
|
<div id="config_error_page" class="flex full-page">
|
|
<div class="new-style">
|
|
<div class="pitch">
|
|
<h1>
|
|
{{ _("Configuration error") }}
|
|
</h1>
|
|
</div>
|
|
<div class="white-box">
|
|
<div class="errorbox config-error">
|
|
<div class="errorcontent">
|
|
<p>
|
|
{% block error_content %}
|
|
{% endblock %}
|
|
</p>
|
|
|
|
<p>After making your changes, remember to restart
|
|
the Zulip server.</p>
|
|
<p><a href=""> Refresh</a> to try again or <a href="{{ go_back_to_url }}">go back to {{ go_back_to_url_name }}</a>.</p>
|
|
</div>
|
|
|
|
</div>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
{% endblock %}
|