Right now, ErrorPageError *assumes* you're never running on the cli or the API. It's kinda a crappy superclass to use for errors unless you're 1000% sure you'll never hit that code path. Yay assumptions! Ideally, all of this report() crap is cleaned up and unified across the like 1192902117 places we have it spread out, but for now just detect the scenario and delegate back to MWException, which does the right thing Bug: T168337 Change-Id: Ia2f490528e128527a7a5ef1f4f5eea36ec9ee810 |
||
|---|---|---|
| .. | ||
| BadRequestError.php | ||
| BadTitleError.php | ||
| ErrorPageError.php | ||
| FatalError.php | ||
| HttpError.php | ||
| LocalizedException.php | ||
| MWContentSerializationException.php | ||
| MWException.php | ||
| MWExceptionHandler.php | ||
| MWExceptionRenderer.php | ||
| MWUnknownContentModelException.php | ||
| PermissionsError.php | ||
| ReadOnlyError.php | ||
| ThrottledError.php | ||
| UserBlockedError.php | ||
| UserNotLoggedIn.php | ||