{% from '_maintenance_fields.html' import maintenance_fields with context %} {% set page_title = 'Maintenance conflict' %} {% include '_header.html' %} {#- The refused write (ADR-0014 amendment). Two refusals land here, because the admin's situation is the same in both: **nothing was written**, and their own words are still theirs. One is the compare-and-set — the token the form carried no longer matches the stored pin, so both texts are shown, the stored one named and dated, and the re-submit carries the **refreshed** token. Two forms rather than one clever one: taking the stored words is a plain one-click submit, so it needs no JavaScript and no server-side "which field wins" rule. The other is an **expiry we will not accept** (`problem`): not one of the explicit duration/calendar forms, not in the future, or longer than a year. A zero or negative window used to be written happily and then swept away a tick later, taking the reason and both authorships with it — a lost explanation behind a redirect that looked like success, which is exactly what this page exists to make impossible. Here the token is unchanged, because nothing about the stored pin moved. -#}
Nothing was saved. {{ problem }}
Nothing was saved. {{ stored.set_by or 'Someone else' }} changed this pin {{ stored.set_at | localtime }}, after the form you submitted was drawn.
Pinned by {{ stored.created_by or 'unknown' }} {{ stored.created_at | localtime }}; expires {{ stored.expires_at | localtime }}.
No explanation was given.
{% endif %}You asked to clear a pin that is no longer the one above. Clear it anyway, or leave it as it stands.
Leave it pinned {% else %}Nothing was saved. The pin you were working on is gone — someone cleared it, or it expired — so this node is not in maintenance at all.
There is nothing left to clear.
Back {% else %}