Details
-
Type:
Task
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0
-
Fix Version/s: 2.0
-
Component/s: Administration
-
Labels:None
-
Affected Branches:MOODLE_20_STABLE
-
Fixed Branches:MOODLE_20_STABLE
Description
With the introduction of exceptions and new output lib routines there are some new problems that need to be solved in error, exception and debug handling. There were also multiple old problems we could not solve earlier because of the backwards compatibility requirements.
I was maintaining the lib/setup.lib and friends since 1.6.x and I intend to continue to do that in 2.0 too 
For more info see:
- http://moodle.org/mod/forum/discuss.php?d=135177
MDL-12886(web service servers need to use custom exception handlers)- MDL-20531
Issue Links
| This issue is duplicated by: | ||||
| MDL-20645 | Cleanup error and debugging messages |
|
|
|
Activity
- All
- Comments
- History
- Activity
- Source
- Test Sessions
About different default exception handlers (normal web requests one, web-services one...) just noting that perhaps it would be nice to have them under some umbrella, able to perform common tasks for all them automatically, like the transactions thing (MDL-20625) and other friends that must be processed by all the handlers in the same way.
Ciao
ah sure, already started working on this abstraction yesterday
Also... from some days ago... MDL-20577
for your consideration about to put it here/close whatever. ciao
There was a proposal to use 503 instead of 404 in fatal error, it is not correct - the 503 in "early_error" means moodle can not work at all because the error occurred early in lib/setup.php, the other fatal errors mean that something is wrong, most probably something does not exist any more which means moodle is working but something is not available any more.