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.
43 lines
1.5 KiB
Cheetah
43 lines
1.5 KiB
Cheetah
{{template "base/head" .}}
|
|
<div class="organization settings delete">
|
|
{{template "org/header" .}}
|
|
<div class="ui container">
|
|
<div class="ui grid">
|
|
{{template "org/settings/navbar" .}}
|
|
<div class="twelve wide column content">
|
|
{{template "base/alert" .}}
|
|
<h4 class="ui top attached warning header">
|
|
{{.i18n.Tr "org.settings.delete_account"}}
|
|
</h4>
|
|
<div class="ui attached warning segment">
|
|
<div class="ui red message">
|
|
<p class="text left"><i class="octicon octicon-alert"></i> {{.i18n.Tr "org.settings.delete_prompt" | Str2html}}</p>
|
|
</div>
|
|
<form class="ui form ignore-dirty" id="delete-form" action="{{.Link}}" method="post">
|
|
{{.CsrfTokenHtml}}
|
|
<input class="fake" type="password">
|
|
<div class="inline required field {{if .Err_Password}}error{{end}}">
|
|
<label for="password">{{.i18n.Tr "password"}}</label>
|
|
<input id="password" name="password" type="password" autofocus required>
|
|
</div>
|
|
<div class="ui red button delete-button" data-type="form" data-form="#delete-form">
|
|
{{.i18n.Tr "org.settings.confirm_delete_account"}}
|
|
</div>
|
|
</form>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
|
|
<div class="ui small basic delete modal">
|
|
<div class="ui icon header">
|
|
<i class="trash icon"></i>
|
|
{{.i18n.Tr "org.settings.delete_org_title"}}
|
|
</div>
|
|
<div class="content">
|
|
<p>{{.i18n.Tr "org.settings.delete_org_desc"}}</p>
|
|
</div>
|
|
{{template "base/delete_modal_actions" .}}
|
|
</div>
|
|
{{template "base/footer" .}}
|