ScoutsTracker now supports the Claim the Flame challenge under “Home” | “Seasonal challenges”.

SS-3933: When deleting a youth, if there are other youth with similar names, the user is warned about the fact and shown the similar names. This then helps them confirm that they aren't deleting the wrong “Ethan”.

SS-3982: Add an “Apply to all upcoming events” button to “Account” | “Advanced” | “Default Scouter-in-charge”, so if the Scouter-in-charge wasn't different for some of the events, they can quickly be replaced. This is useful when you have a leadership change. Changing the Scouter-in-charge prompts you if you want to apply the change to any upcoming events if some of those events have a different Scouter-in-charge.

Wired off the creation of “personal” accounts. The existence of these accounts were a hold-over from when Sections/Groups had to individually pay for ScoutsTracker, and consequently there were situations when the Youth wanted to track their own progress, even though the Scouters didn't want to pay. But now that National is covering the licence fee, this is no longer a common situation, and is instead being used by parents who forgot their login.

Deleted old databases and tables that were still being retained from this summer's big schema migration.

• Added better reporting of global-block rejections
• Moved updating of message status to “sent” to the ResponseParser, and added polling loop to client
• Added support for “Safety” section in a custom badge definition's Notes field
• Cleaned up some use of apostrophes in HTTP params
• Reduce amount of uploaded outing data when cancelling, updating member-in-charge, etc.
• Reduce number of times EMAIL_META gets upload to server
• Deleted old databases and tables that were still being retained from this summer's big schema migration

• SS-3394: Changing your own login to use an email address already associated with another login shows a dialog, but the “Continue” button wasn't working
• Assertion when updating EMAIL_META
• COMMITTEE: SS-3949: Group-wide progress report was reporting a 500 error
• COMMITTEE: SS-3954: Pandemic stage colours weren't being set correctly
• SS-3947: Incorrect edition recorded when logins moved up to next section
• Could get caught in an endless login loop if events had been misstored with account ID = 0
• SS-3956: Red-herring error message when transferring youth to another account
• SS-3959: Deleting an attachment doesn't immediately update the list of attachments, causing one to believe it didn't get deleted
• SS-3972 (and others): Events appeared to go missing after signing in
• Bogus events could prevent /hello website from loading
• SS-3973: Yet another SC website redesign resulted in broken links to documents
• COMMITTEE: Email invitations to collaborate weren't including the required invitation key
• The list of other logins in the “You have no logins” page could be empty for some users