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

rearrange control panel

Browse Source
This commit is contained in:
Philip Sargent 2022-12-21 15:29:57 +00:00
parent ec040824f6
commit d06af5b0ec
2 changed files with 21 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
templates/base.html
View File

@ -50,8 +50,8 @@
<a href="{% url "stats" %}">statistics</a> |
<a href="/wallets/year/2022">Wallets(2022)</a> |
<a href="{% url "expedition" 2022 %}">Expo(2022)</a> |
<a href="{% url "controlpanel" %}">import/export</a> |
<a href="/admin/">Django admin</a>
<a href="{% url "controlpanel" %}">Control panel</a> |
</div>
<div id="nav">

28
templates/controlPanel.html
View File

@ -19,24 +19,31 @@
{{ error }}
</div>
{% endif %}
<h3>Administration Utilities</h3>
<ul>
<li><a href="/pathsreport">Folder paths used</a> -folders settings used by this troggle installation
<li><a href="/dataissues">Data Issues on Imports</a> - warnings and errors from recent data import
<li><a href="/admin/">Django admin</a> - Deep magic access to all models and data
</ul>
<h3>This control panel is being redeveloped</h3>
<p>Do not attempt to use any of these functions as they are in active development.
<p>Do not attempt to use any of these import functions as they are in active development.
<ol>
<li>Importing things in the wrong order will screw-up the database links and break things.
<li>The export of logbooks in a standard HTML-like format is very much not working.
<li>We are working on an on-line importer for new logbook entries - with syntax checking.
<li>We are working on an on-line importer for new survex files - with syntax checking
<li>Logbooks can only be <em>exported</em> in the current format.
</ol>
<p>Today (Jan. 2022) we use the <a href="/handbook/troggle/trogimport.html">databaseReset program</a> to import from the master files. This is run on the server itself only by nerds who remotely log in to the server using ssh.
<p>Today (Dec. 2022) we use the <a href="/handbook/troggle/trogimport.html">databaseReset program</a> to import from the master files. This is run on the server itself only by nerds who remotely log in to the server using ssh.
<p>Before you even think about doing database imports, you should understand the implications on everyone else. See <a href="/handbook/troggle/trogindex.html">the Troggle documentation</a>.
<p>As soon as you can cope, you should read the source code for
<a href="http://expo.survex.com/repositories/troggle/.git/tree/databaseReset.py">databaseReset</a> to see what it does, as the details are not documented anywhere else yet. But at least the code is quite well commented.
<p>There is currently no feedback here when an import failure occurs - even a catastrophic one. You can see the list of parsing errors on the most recent imports on the <a href="/dataissues">Data Issues</a> page.
<font style="color: silver">
<p>The logbook export capability is used to convert an archaic logbook into the new logbook format. When all the old logbooks have been converted, we won't need this any more. (Neither will we need the old format parser).
<div style="column-count: 2; ">
<font style="color: silver">
{% comment %}
<form name="reset" method="post" action="">
{% csrf_token %}
@ -97,10 +104,10 @@
</form>
<p>&nbsp;
<p></font>
<h3>Export to a different format:</h3>
<hr />
<h3>Export Logbook to a different format:</h3>
<p>This creates 'logbook-new-format.html' in the years/&lt;year&gt;/ folder
<table>
<tr>
@ -139,6 +146,9 @@
</table>
</form>
<p>&nbsp;
<p>&nbsp;
<p>&nbsp;
</div>
</font>
{% endblock %}