Fixed: saving an edited backup job
On the job edit page, Save changes did nothing in the browser — the changes were discarded without a message, for every kind of job (#9 — thanks to @woutervanrooy for the report). A stray closing form tag in the page ended the form before its buttons, so the browser no longer connected the button with the form. The problem came with the separate edit page in 0.38.0. Editing works again.
Better checks before every release
Our tests and the release QA sent the forms directly to the console, so they passed although the button did nothing in a browser. They now also read every page the way a browser does: each button must belong to its form, ids must be unique, no template text may be left over, and every edit page — sent back unchanged exactly as a browser sends it — must save and show the same values. The same check runs against the QA console with real data before each release. It also found the sidebar clock and a guide section sharing one id, which made the guide's link to that section jump to the clock; fixed.
Releases are signed with the BackupZit release key; consoles verify them before installing.