xle/troggle-unchained
2
0
Fork 0
forked from expo/troggle
Code Issues 4 Pull Requests Projects 1 Wiki Activity

warning message to people who have got here before they are ready, and link to docm

Browse Source
This commit is contained in:
Philip Sargent 2023-07-22 22:26:50 +03:00
parent f76c22e843
commit 3ffb07371d
1 changed files with 48 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
templates/editcave.html
View File

@ -1,10 +1,57 @@
{% extends "cavebase.html" %} {% extends "cavebase.html" %}
{% block title %}Edit Cave - {{cave.official_name|safe}} - {{cave.kataster_number}}{% endblock %}
{% block title %}
{% if cave.official_name %}
Edit Cave - {{cave.official_name|safe}} - {{cave.kataster_number}}
{% else %}
New Cave Creation Form
{% endif %}
{% endblock %}
{% block extraheaders %} {% block extraheaders %}
{% include 'html_editor_scripts_css.html' %} {% include 'html_editor_scripts_css.html' %}
{% endblock %} {% endblock %}
{% block content %} {% block content %}
{% if cave.official_name %}
<h1>Edit Cave - {{cave.official_name|safe}} {{cave.reference}}</h1> <h1>Edit Cave - {{cave.official_name|safe}} {{cave.reference}}</h1>
<p>The fields on this form, two of which are vital, are documented explicitly on the page
<a href="/handbook/survey/caveentryfields.html">cave entry fields</a>
and these same fields appear in the alternative file upload process as described in
<a href="/handbook/survey/newcavefile.html">new cave file</a>.
<p>As it says there,
<em>"There are a lot of fields on the 'new/edit cave' page and the 'new/edit entrance' page and some of them are a quite mysterious.
<a href="/handbook/survey/caveentryfields.html">This page</a> explains what they mean."</em>
{% else %}
<h1>New Cave Creation</h1>
<div style="padding: 20px; border: 2px solid red;">
<b>
<p><font style="color: red">WARNING</font>
<p>This form is the <font style="color: red">SIXTH</font> step in
the expo online cave recording system.
<p>The whole process starts at step <font style="color: blue">ONE</font> here: <a href="/handbook/survey/newcave.html">Great, I have discovered a new cave...</a>.
<p>But even if you are happy and confident that you have understood steps 1 to 5, please go through the recommended procedure
of editing an existing cave entry first, before trying to create a totally new one.
This is described under the section "Recommended procedure" on the page <a href="/handbook/survey/caveentry.html">CaveEntry</a>
especially sub-heading "Edit Cave form" and please go through the example edit process for caves
Plateauh&ouml;hle 171 and Plateauh&ouml;hle 172, as described there.
<p>
If you have not done all the preceeding steps, cancel this form and go back and do them now.
Click <a href="/handbook/survey/newcave.html">here</a>.
</b>
<p>This form contains many esoteric and non-obvious data requirements, which will give you a
frustrating time if you try to persist without being familiar with how all the bits fit together.
<p>The fields on this form, two of which are vital, are documented explicitly on the page
<a href="/handbook/survey/caveentryfields.html">cave entry fields</a>
and these same fields appear in the alternative file upload process as described in
<a href="/handbook/survey/newcavefile.html">new cave file</a>.
<p>As it says there,
<em>"There are a lot of fields on the 'new/edit cave' page and the 'new/edit entrance' page and some of them are a quite mysterious.
<a href="/handbook/survey/caveentryfields.html">This page</a> explains what they mean."</em>
</div>
{% endif %}
{% include 'html_editor_pop_ups.html' %} {% include 'html_editor_pop_ups.html' %}
<h2>{{message}}</h2> <h2>{{message}}</h2>
<form action="" method="post">{% csrf_token %} <form action="" method="post">{% csrf_token %}