← All releases
Sixteen changes and no database migrations. This is an imports release: two faults that were quietly writing wrong data during a roster import are fixed. One of them moved dates back a hundred years, and it needed nothing more than re-importing a file the site itself produced.
What's new on the site
Importing rosters and training records
- A future date no longer moves back a hundred years on import. A position ending 2026-12-01 was stored as 1926-12-01, and the import reported success. Exporting your roster and re-importing the file unedited was enough to trigger it — no typing mistake required. The rule that reads a two-digit year as this century was being applied to four-digit years as well; it now only applies where the year is genuinely two digits.
- What it cost. Position of Responsibility end dates were silently wrong, and training records were duplicated: an import that could not recognize the shifted date treated the same training as new and added it again.
- What is not fixed yet. This stops it happening again. It does not repair dates already stored wrong. A repair for those is planned.
- Every importer now recognizes a member the same way. Ten separate importers each decided "is this person already in the troop?" their own way, and they disagreed. The same file, in the same troop, could match a different person depending on which importer you used.
- The worst case was two members with the same name. One importer refuses to guess and leaves the row for you. Another took whichever row it found first and wrote to it, with nothing on the screen to say a choice had been made. All ten now share one rule, and the refusal-to-guess behavior is the one that won.
The phone app
- Dates on the offline events list match the rest of the site. When the phone app showed events from its saved copy, it wrote the dates in a different format from the same page loaded normally. They now read the same either way.
Accessibility
- Screen readers are no longer told you are on two pages at once. The breadcrumb bar at the top of a page marked every crumb without a link as "the page you are on", instead of just the last one. Sighted users saw nothing wrong and nothing looks different now; a screen reader announcement is simply correct.