troggle/templates/login/register.html

{% extends 'base.html' %}

{% block content %}
<!-- this overrides the django.contrib.auth default  form
and it must be placed in 
troggle/templates/login/register.html
because magic 

This is because Django is Opinionated and does lots of Invisible Defaults
see 
https://docs.djangoproject.com/en/5.0/topics/auth/customizing/#using-a-custom-user-model-when-starting-a-project
-->
<script>
function myFunction() {
  var x = document.getElementById("id_password1");
  if (x.type === "password") {
    x.type = "text";
  } else {
    x.type = "password";
  }
  var x = document.getElementById("id_password2");
  if (x.type === "password") {
    x.type = "text";
  } else {
    x.type = "password";
  }
}
</script>
<style>
input, textarea {font-family: monospace; font-weight: bold; text-align:right; font-size: 100%; padding: 0.5em;  }
textarea {text-align:left }
input[type="checkbox"] {
	transform: scale(1.7);
	margin: 10px;
	}
li {color:red}
</style> 
	
<div class='middle'>
<h2>{% if newuser %}
New User Registration <br />for someone who has never attended Expo
{% else %}
User Registration - for a personal login to Troggle
{%endif %}</h2>
<!--using template login/register.html -->
</div>

<h3>Register your email address</h3>
{% if unauthorized %}
<span style="color:red">
UNAUTHORIZED attempt to change password or email address. <br />
You are not logged in as the user you are attempting to re-register.
</span>{% endif %}

{% if newuser %}
<p>You need to register before you can fill out the 'signup' form to request to attend Expo.
{% else %}
<p>For previous expoers, your username must be your 'troggle id' as listed on the <a href='/people_ids'>past expoers list</a>
<p>For new people wanting to come to expo for the first time, please use the <a href="/accounts/newregister/">New User</a> registration form
{%endif %}
<p>This will eventually sign you up automatically to the 
<a href="https://lists.wookware.org/cgi-bin/mailman/roster/expo">expo email list</a>. 
So type in the same email address that you use there if you have already signed up to that.
<p>
<span style="color:red">
{{ warning }} 
</span>

<div style='width: 700px; font-family: monospace; font-weight: bold; font-size: 150%; text-align: right; '>
    <form  method="post" accept-charset="utf-8">{% csrf_token %}
    {{form.as_p}}

<div class='align-right'>
{% if newuser %}
{% else %}
	<input type="checkbox" checked name="visible" onclick="myFunction()">Make Passwords visible (on this form only)
{%endif %}
	<br /><br />
{% if newuser %}
	
	<button  class="fancybutton"  style="padding: 0.5em 25px; font-size: 100%;" 
		onclick="window.location.href='/accounts/password_reset/'" value = "Go to" >
		Get login token by email &rarr;
	</button>
{% else %}
	<button  class="fancybutton"  style="padding: 0.5em 25px; font-size: 100%;" 
		onclick="window.location.href='/accounts/password_reset/'" value = "Go to" >
		Reset password
	</button>
	&nbsp;&nbsp;&nbsp;
	<button  class="fancybutton"  style="padding: 0.5em 25px; font-size: 100%;" type = "submit" >
		Register &rarr;
	</button>
{%endif %}
</div>
</form>
</div>
<div style='width: 50em' align="left">
<h3>Your name</h3>
{% if newuser %}
<p>Use the name you are usually known by "officially": this is usually the name on your passport. 
But if you habitually use your second forename, not the first forename, use that. 
Yes, you can put in any 'de', 'van' or 'von' or whatever 'nobiliary particle' you have, or a hyphenated surname; but this must be your real name. 
Nicknames and fun names are done later.
{% else %}
<p>For previous expoers, your username must be your 'troggle id' as listed on the <a href='/people_ids'>past expoers list</a>
{%endif %}
<p>Unfortunately cavers tend to use weird and playful names when signing up for things, 
so we can't automatically connect the troggle names and ids with the email addresses 
on the email list. And we don't believe in signing people up for things without their
direct permission anyway.
Having said that, when you register here we <em>will</em> sign you up automatically to 
the expo email list as that is how expo manages everything and it is a condition of 
coming on expo. (You can unsubscribe from the email list after expo.)

<p>But the automatic sign-up to the email list is not working yet, and may not be before April 2025. 
So if you don't want to miss out on anything important, make sure you sign up to the 
<a href="https://lists.wookware.org/cgi-bin/mailman/roster/expo">email list</a>
right now.

<h3>Students !</h3>
Please do not use an email address which will expire when you leave your current institution.
This will happen much sooner than you can possibly believe. If you realise that you have done this on the email list, 
you can change it at the bottom of <a href="https://lists.wookware.org/cgi-bin/mailman/listinfo/expo">this page</a>.

{% if newuser %}
<h3>What happens next</h3>
<p>Clicking the big blue button will send you an email which will contain a login token.
Click on the link in the email and you will be able to set your own login password. 
Use this to login to troggle and go to the Expo Signup form.
{% else %}
{%endif %}

<h3>Security note</h3>
We never store passwords at all, we only store a cryptographic hash. 
We do store your email address but only 'in clear' inside the live database online
where it is accessible only to the database administrators. There is no troggle report
which publishes your email address. 
For permanent storage all email addresses are encrypted. Your real name and troggle
username is public however, and we do not have anonymous people attending expo.
<p>The password we 
{% if newuser %}will be{% else %}are{%endif %}
asking for is used only to log on to troggle to keep track of
who is editing the current expo records, website content, historic survey data and 
when using the expo kanban software. It is not the same as the password to access your email 
with your email provider
and it is not the same as the password you use to interact with the expo 
<a href="https://lists.wookware.org/cgi-bin/mailman/roster/expo">email list</a>.

<span style="color:red">
{{ form.non_field_errors }} <!-- form validation errors appear here, and also at the top of the form-->
</span>
</div>

{% endblock %}