app/templates/error/400.html

{% extends "withoutnav_template.html" %}
{% block per_page_title %}Bad Request{% endblock %}
{% block maincolumn_content %}
<div class="grid-row">
    <div class="column-two-thirds">
      <h1 class="heading-medium">
            {{ message|join(",")}}
        </h1>
    </div>
</div>
{% endblock %}
Added a new 400.html error page, this error page will only be used when we get an HTTPError from the api. This was done to solve the problem of invitations expiring and the user getting a 500 error message, which says to try again. 2016-12-07 14:00:03 +00:00			`{% extends "withoutnav_template.html" %}`
Fix page titles that didn’t get fixed before Did most of this work in: https://github.com/alphagov/notifications-admin/pull/1118 > In pages specific to a service (e.g. dashboard and sub pages) the > title needs to distinguish which service it applies to. This is mainly > to give context to screen reader users who could be managing multiple > services. > > Implementing this uses template inheritance: > > `page_title` includes `per_page_title` includes `service_page_title` > > ‘GOV.UK Notify’ is inserted into every page title. > > Pages that set `service_page_title` get the service name inserted too. 2017-02-23 15:34:13 +00:00			`{% block per_page_title %}Bad Request{% endblock %}`
Added a new 400.html error page, this error page will only be used when we get an HTTPError from the api. This was done to solve the problem of invitations expiring and the user getting a 500 error message, which says to try again. 2016-12-07 14:00:03 +00:00			`{% block maincolumn_content %}`
			`<div class="grid-row">`
			`<div class="column-two-thirds">`
			`<h1 class="heading-medium">`
			`{{ message\|join(",")}}`
			`</h1>`
			`</div>`
			`</div>`
			`{% endblock %}`