troggle/templates/errors/svxcavesingle404.html

<!-- errors/svxcavesingle404.html - this text visible because this template has been included -->
{% extends "base.html" %}
{% block title %}Troggle Error - Bad Cave ID{% endblock %}

{% block content %}

<h1>Cave Identifier not found in database</h1>

<h3>Cave identifier looked for: <font color="red">'{{cave}}'</font></h3>
<ul>
<li>- unofficial number like this not found</li>
<li>- kataster number like this not found</li>
</ul>

<h3>You probably got here because a survex (.svx) file has been stored on the server in the 
<a href="/handbook/computing/repos.html"><var>:loser:</var></a> repository 
but whoever was 
responsible has not yet created the appropriate XML file the 
<a href="/handbook/computing/repos.html"><var>:expoweb:</var></a> repository 
which registers the cave description and ties together
the survex files with everything else.
</h3>

<p>The process for registering a new cave is documented in 
<a href="/handbook/survey/caveentry.html">this part of the survey handbook</a>.
<p>
<p>It is also possible that the cave description page is being viewed using an alternative URL,
so that the local links in the page to other parts of the cave do not work.
<br>
e.g. /cave/1623-161 is not the correct way of looking at Kaninchenhohle, 
<br>
you should be using <br>
/1623/161/top.htm instead.
<p>If that is the case, tell a nerd that we haven't fixed the fault that we thought we had fixed.
	<div class='space'><p>&nbsp;</div>
        
		<h3>What you should do now</h3>
    <p>Please report the error by emailing the nerds at 
        <a href="mailto:expo-tech@lists.wookware.org">expo-tech@lists.wookware.org</a> with this information:
        <ol>
        <li>The error message written in <font color="red">red</font> above.
        <li>The previous page URL: <font color="red">
<script type="text/javascript">
    document.write(document.referrer);
</script></font>
        <li>Go back to this previous page <script type="text/javascript">
        document.write("<a href='",document.referrer,"'>",document.referrer,"</a>");
        </script>
        and see if you can tell whether the bad page reference was in HTML text which had been written manually, or whether it appeared to be a programming error.
        </ol>

{% endblock %}