While in read-only mode, most OperationalErrors were caught correctly but /users/login threw an Apache-level 500 error.
Assignee: nobody → james
Target Milestone: 2011Q1 → 2.6
commonware: https://github.com/jsocol/commonware/commit/b98d6b vendor lib: https://github.com/jsocol/kitsune-lib/commit/d20ec40 We'll need to flip on read-only mode to verify (along with bug 633401). In this case, going to /users/login in read-only mode should show a "Maintenance Mode" error instead of an Apache-style 500 error.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Verified maintenance page displays for login on login page, AAQ, and any forms that require being logged in.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.