According to the following article, this seems to be the normal CakePHP-way.
http://nuts-and-bolts-of-cakephp.com/2008/08/29/dealing-with-errors-in-cakephp/
So, errors are only displayed to the programmer while developing, and
not to the user while surfing. If you want to display something
Just curious, why the --psybear at the end of your message subjects?
Google does put in your name and email address for you. ;)
On Feb 24, 8:59 am, Joshua Muheim psybea...@gmail.com wrote:
According to the following article, this seems to be the normal CakePHP-way.
Thanks for your reply, Steve. I have created app/app_controller.php
with the following content:
?php
class AppError extends ErrorHandler {
function error500($params) {
header('HTTP/1.1 500 Internal Server Error');
$this-_outputMessage('error500');
}
}
?
But it still doesn't work,
Hey everybody
When having DEBUG set to 2 (or 1), my sweet little error500 is shown
correctly.
SomeController extends AppController {
function _error500() {
$this-cakeError('error500');
exit;
}
}
But when it's set to 0, then I'm just getting a plain Error: The
I think you need to provide a appError class. The default code turns off
the error routing when you disable DEBUG ( set it to 0 ) so it looks for
a URL which your server is correctly reporting the absence of.
http://book.cakephp.org/view/154/Error-Handling
On Tue, 2011-01-25 at 08:21 -0800,
