Notes from building KNJ Panel, in the order it actually happened.
blog /blɒɡ/ noun — 1. A web log. 2. Here: a build log. What we built, what broke, and what we learned.
Two sections of the sidebar could fold up out of the way. Every other section, in both the admin panel and the account panel, was stuck open forever…
Read more →A server had six real packages sitting there, ready to install. Its own row said “Completed.” Not wrong, exactly — the last thing that had happened to it…
Read more →Two update-related controls for this server lived in two different places. One card listed every other server and let each be checked, updated and rebooted from one screen.…
Read more →Three releases were cut back to back and a linked test server was updated to the latest one, but its row still said an update was waiting. It…
Read more →Panel Updates could already push a panel software update to every linked DNS-only and Mail-only server from one screen. System Updates, the neighboring page that manages OS package…
Read more →A feature request born from watching the clock. Scanning a large account for the first time took about twenty minutes, and the entire time both sides of the…
Read more →Until now, bugs in this project had come from the person building it using the panel the way it was meant to be used. This batch is the…
Read more →A broken webmail inbox turned up during live use: after a first subject-based mail rule delivered its first message, the account’s folders stopped loading. The mail itself was…
Read more →A small gap, found while reviewing the live admin pages. The Malware Scan Overview page had stats, security status and recent findings, but no way to start a…
Read more →Noticing unusual CPU use in the Resource Monitor led to a gap in two security features at once, both traced to the same root cause: they had been…
Read more →The Malware Scan and Backups sidebar entries had already been folded from several rows into one tabbed parent, each as a side effect of building something else. Feedback…
Read more →The brief was simple to state and hard to verify: a shield that stays lit, with a glow that rotates around its edge, colored by how much attention…
Read more →The scheduled scanner had been running for a day, quarantining and suspending where appropriate, but doing all of it silently. Nobody was told anything unless they went looking.…
Read more →Two unrelated reports landed the same evening, and both turned out to be the same kind of mistake: something that should have happened all at once was happening…
Read more →Testing this feature against a real account for the first time, rather than a sandbox built to exercise it, turned up two places where a reasonable assumption was…
Read more →The routing fix from earlier the same day worked. Double-checking it by using the support access mode, which lets staff see exactly what a customer sees without needing…
Read more →A tester’s job, done well, is trying the thing nobody else got around to yet. That’s what turned this one up: not a code review or an automated…
Read more →After the previous fix, the signup form still failed with the same browser error. It is tempting to assume the same bug, but several causes can look identical…
Read more →A restyled signup form, intended to confirm in place without a page reload, stopped working entirely. Cause A plain form navigation can cross sites freely, but a script…
Read more →During testing, a mail filter rule ran for the first time after a mailbox had been moved, and folder listing for that mailbox then failed. Cause When a…
Read more →