2dc6f15eca
The choice regarding which forms should or should not trigger a warning is subjective. I tried to be consistent and not warn about forms that: - run an action, rather than edit data: search, send an email. - delete data: a warning about losing data would be confusing Note that forms on sign-in pages were already ignored (using a selector, rather than an explicit class on the form element). Fixes #3698.
32 lines
1.1 KiB
Cheetah
32 lines
1.1 KiB
Cheetah
{{template "base/head" .}}
|
|
<div class="user reset password">
|
|
<div class="ui middle very relaxed page grid">
|
|
<div class="column">
|
|
<form class="ui form ignore-dirty" action="{{.Link}}" method="post">
|
|
{{.CsrfTokenHtml}}
|
|
<input name="code" type="hidden" value="{{.Code}}">
|
|
<h2 class="ui top attached header">
|
|
{{.i18n.Tr "auth.reset_password"}}
|
|
</h2>
|
|
<div class="ui attached segment">
|
|
{{template "base/alert" .}}
|
|
{{if .IsResetForm}}
|
|
<div class="required inline field {{if .Err_Password}}error{{end}}">
|
|
<label for="password">{{.i18n.Tr "password"}}</label>
|
|
<input id="password" name="password" type="password" value="{{.password}}" autocomplete="off" autofocus required>
|
|
</div>
|
|
<div class="ui divider"></div>
|
|
<div class="inline field">
|
|
<label></label>
|
|
<button class="ui blue button">{{.i18n.Tr "auth.reset_password_helper"}}</button>
|
|
</div>
|
|
{{else}}
|
|
<p class="center">{{.i18n.Tr "auth.invalid_code"}}</p>
|
|
{{end}}
|
|
</div>
|
|
</form>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
{{template "base/footer" .}}
|