AdminBug reports 23Suggestions 4Exploits 0
Fixed on the website in b4ededb, and deployed.
Cause: the category was optional on both sides. The server explicitly permitted an empty one, and the dropdown carried no 'required' flag - so most reports arrived uncategorised and the board's category filter was close to useless.
Fix, in order of what actually matters:
- The server is the real gate: an empty category is now its own rejection with a plain-English message, and a value that is not a real category still says 'Unknown category'. A client-side 'required' alone would have fixed nothing, since a direct POST bypasses it.
- The form marks the field required, and its label badge switches from the grey 'optional' pill to the pink 'required' pill already used by the title and description fields. No layout change.
Retest on the report form: try submitting with the category left on its blank entry.