{% load i18n admin_errors_tags %}

{{ original.exception_type }} {{ original.title }}

{% if original.culprit %}

{{ original.culprit }}

{% endif %}
{% ae_level_badge original.level %} {% ae_status_badge original %}
{% translate "Count" %}
{{ original.count|ae_compact_number }}
{% translate "First seen" %}
{{ original.first_seen|timesince }} {% translate "ago" %}
{% translate "Last seen" %}
{{ original.last_seen|timesince }} {% translate "ago" %}
{% if ae_can_change or ae_can_delete %} {% comment %} The change-form page already wraps this include in the admin's own
; nesting another there is invalid HTML and browsers silently misparse it (the button ends up submitting to the outer form's action instead of ours). `formaction`/`formmethod` on the buttons target our status URLs without opening a new form, so they work whether or not an ambient form is present. The event-detail page (no ambient form) opts into one real wrapping via `ae_standalone_actions` so the buttons still have somewhere to submit from. {% endcomment %}
{% if ae_can_change %} {% if ae_standalone_actions %}{% csrf_token %}{% endif %} {% if ae_standalone_actions %}{% endif %} {% endif %} {% if ae_can_delete %} {% translate "Delete" %} {% endif %}
{% endif %}