Website v1.0.6¶
For everyone: what changed in this release of the website. Released 2026-10-23.
Highlights¶
The contact and course registration forms are friendlier and safer. They explain what is wrong in plain words, work better with screen readers, and now limit how often one connection can send them.
Features¶
- Every field on both forms now has a label that screen readers announce, including fields where the design shows only the placeholder text.
- Course registration asks for applicants to be 18 or older. Under-18 birth dates are refused with "You must be 18 or older to register."
- The contact form now needs a phone number, as the registration form already did.
- A connection can send at most 20 submissions an hour on each form. After that the form says "Too many submissions from this connection. Try again in N minutes." and works again when the time is up. Ordinary visitors will not notice this.
- A person who registers twice with the same email address sees the same success message. Nothing new is stored, and staff receive an email headed "Repeat registration" with the details that were sent again and the date of the first registration.
- No more than five confirmation emails are sent to one email address in a day. When a sixth would be due, the submission is still accepted, and the staff email says "No confirmation email was sent: this address has had five today."
- If a content or ad blocker stops the spam check from running, the form now says "The spam check could not run. If you use a content or ad blocker, allow this site and try again."
Fixes¶
- Names, phone numbers and other fields accept the ordinary things people type (extra spaces, a space in a phone number, a short name like "Ann"). Rules are the same in the browser and on the server, so a form no longer passes in one place and fails in the other.
- Optional fields left empty or filled with spaces are saved with no value, not as blank text.
- The registration form is empty again when the visitor closes the success dialog (title and country empty, gender back to "Prefer Not to Specify"), so a second registration works without reloading the page.
- Errors appear next to the field they belong to, with the form-wide message above the submit button.
- A slow or blocked spam check no longer leaves the form waiting for ever.
Operations¶
- One migration,
0002: aform_throttletable for the limits; email addresses are now unique regardless of capital letters; the title and gender of existing registrations are stored as codes (for examplemr,prefer-not-specify) with checks on the title, gender and country; the contact phone number is required. - The deployed image sets
REFUSE_BYPASS_FLAGS=true, so ifEMAIL_BYPASSorRECAPTCHA_BYPASSis set inapp_env, the pages keep serving but the health check and every form submission fail until it is removed (the log names the flag), and the deploy goes red.RECAPTCHA_HOSTNAMES(defaultsleev.org,dev.sleev.org) lists the hostnames accepted for a verified spam check. See Configuration. - nginx on the server also limits POST requests to the website, per address, as a backstop behind the app's own limits. See Infrastructure.
Upgrade notes¶
- Developers who have
EMAIL_BYPASSorRECAPTCHA_BYPASSin.env.localkeep working locally; only the deployed image refuses them. Playwright tests send their ownx-real-ipheader so they do not share one limit. - Before the prod tag, the operator runs read-only checks on the prod database, because migration
0002fails on any hit:titleorgendervalues that do not map to a code, contact rows with no phone, email addresses that differ only in capital letters, andcountryvalues that are not two capital letters. Any hit is fixed before the release. -
Rolling back to v1.0.5 needs one step first. v1.0.5 stores the title and gender as labels (
Mr.,Male), which the checks added by0002refuse, so every registration would fail. Beforejust rollback, run this on that environment's database:ALTER TABLE website.course_registrations DROP CONSTRAINT course_registrations_title_valid, DROP CONSTRAINT course_registrations_gender_valid;The rest of
0002(the lower-case email index, the required phone, the country check,form_throttle) is harmless to v1.0.5. Rows v1.0.5 writes meanwhile hold labels and must be converted to codes (the sameUPDATEs as in0002) before a new migration can add the constraints back on the next roll-forward. - For a few seconds during the deploy, registrations sent to the old container can fail; the visitor retries. - Runjust provisionin the managed leaf (infra_managed_vps_hostinger) for the website's nginx limit after the release.