mirror of
https://expo.survex.com/repositories/troggle/.git
synced 2024-11-25 16:51:54 +00:00
64 lines
3.2 KiB
HTML
64 lines
3.2 KiB
HTML
{% extends "cavebase.html" %}
|
|
|
|
{% block title %}
|
|
{% if cave.official_name or cave.kataster_number or cave.unofficial_number %}
|
|
Edit Cave - {{cave.official_name|safe}} - {{cave.kataster_number}}
|
|
{% else %}
|
|
New Cave Creation Form
|
|
{% endif %}
|
|
{% endblock %}
|
|
|
|
{% block extraheaders %}
|
|
{% include 'html_editor_scripts_css.html' %}
|
|
{% endblock %}
|
|
{% block content %}
|
|
{% if cave.official_name or cave.kataster_number or cave.unofficial_number %}
|
|
<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öhle 171 and Plateauhö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' %}
|
|
<h2>{{message}}</h2>
|
|
<form action="" method="post">{% csrf_token %}
|
|
<table>{{ form }}
|
|
<!-- begin caveAndEntranceFormSet-->{{caveAndEntranceFormSet}}<!--end caveAndEntranceFormSet--></table>
|
|
<p><input type="submit" value="Submit" /></p>
|
|
</form>
|
|
|
|
{% endblock %}
|