Comment 3 for bug 316295
Revision history for this message
| Dan Garner (dangarner) wrote Re: Error 500 or blank page accessing Schedule | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Having thought about it this is actually a fault of both.
The Debug class should always output E_USER_ERROR to the browser - this is used widely to indicate an error that should cause a halt and output something meaningful to the browser. Currently it is only doing this when Debug is On.
Also the Schedule class currently checks for enabled displays in the __construct. This is OK but it is not good generating a HALT error there - as the message will be outputted before any UI is built.
Solution:
Fix the Debug class to do what was intended.
Improve the Schedule class to delay the output until the displayPage method is called (there by outputting the error within the UI)