<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Better Error Handling with CakePHP</title>
	<atom:link href="http://aidanlister.com/2009/04/better-error-handling-with-cakephp/feed/" rel="self" type="application/rss+xml" />
	<link>http://aidanlister.com/2009/04/better-error-handling-with-cakephp/</link>
	<description>Code is poetry</description>
	<lastBuildDate>Wed, 28 Jul 2010 23:10:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: John</title>
		<link>http://aidanlister.com/2009/04/better-error-handling-with-cakephp/comment-page-1/#comment-1257</link>
		<dc:creator>John</dc:creator>
		<pubDate>Mon, 28 Sep 2009 11:52:23 +0000</pubDate>
		<guid isPermaLink="false">http://aidanlister.com/?p=5#comment-1257</guid>
		<description>Where are you setting the error types (i.e. paypal, logic, payflow, etc,)?  In the controller?</description>
		<content:encoded><![CDATA[<p>Where are you setting the error types (i.e. paypal, logic, payflow, etc,)?  In the controller?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie Nay &#187; Useful CakePHP Tutorial Roundup for June 26, 2009</title>
		<link>http://aidanlister.com/2009/04/better-error-handling-with-cakephp/comment-page-1/#comment-851</link>
		<dc:creator>Jamie Nay &#187; Useful CakePHP Tutorial Roundup for June 26, 2009</dc:creator>
		<pubDate>Fri, 26 Jun 2009 17:21:40 +0000</pubDate>
		<guid isPermaLink="false">http://aidanlister.com/?p=5#comment-851</guid>
		<description>[...] Better Error Handling with CakePHP - Aidan Lister (April 6, 2009) I&#8217;ve been planning a more useful error handling system, and Aidan&#8217;s method is probably the one I&#8217;ll employ now. He tackles the &#8220;all or nothing&#8221; approach to error handling that CakePHP uses by default: every error in development mode, no error in production mode. Aidan creates a de facto &#8216;0.5&#8242; debug mode, allowing errors to be logged (and administrators to be notified) while still displaying user-friendly messages. [...]</description>
		<content:encoded><![CDATA[<p>[...] Better Error Handling with CakePHP &#8211; Aidan Lister (April 6, 2009) I&#8217;ve been planning a more useful error handling system, and Aidan&#8217;s method is probably the one I&#8217;ll employ now. He tackles the &#8220;all or nothing&#8221; approach to error handling that CakePHP uses by default: every error in development mode, no error in production mode. Aidan creates a de facto &#8216;0.5&#8242; debug mode, allowing errors to be logged (and administrators to be notified) while still displaying user-friendly messages. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aidan Lister</title>
		<link>http://aidanlister.com/2009/04/better-error-handling-with-cakephp/comment-page-1/#comment-732</link>
		<dc:creator>Aidan Lister</dc:creator>
		<pubDate>Tue, 09 Jun 2009 21:39:44 +0000</pubDate>
		<guid isPermaLink="false">http://aidanlister.com/?p=5#comment-732</guid>
		<description>Hi Marco,

It would be nice to have all of the error code together, but it&#039;s not possible in 1.2.x.x. In bootstrap.php, we have to assume nothing else is available, thus we can&#039;t use AppError or ErrorHandler objects.

In AppError, we need to define our __construct method which needs access to $this, so we can&#039;t place that code in bootstrap.php.

I hadn&#039;t thought about logging SQL errors, I think they would usually be followed by a PHP error, but it might be worth adding.

I&#039;m told that cake 1.3.x.x will completely rework the error handling, so you&#039;re best off waiting.

Cheers,
Aidan</description>
		<content:encoded><![CDATA[<p>Hi Marco,</p>
<p>It would be nice to have all of the error code together, but it&#8217;s not possible in 1.2.x.x. In bootstrap.php, we have to assume nothing else is available, thus we can&#8217;t use AppError or ErrorHandler objects.</p>
<p>In AppError, we need to define our __construct method which needs access to $this, so we can&#8217;t place that code in bootstrap.php.</p>
<p>I hadn&#8217;t thought about logging SQL errors, I think they would usually be followed by a PHP error, but it might be worth adding.</p>
<p>I&#8217;m told that cake 1.3.x.x will completely rework the error handling, so you&#8217;re best off waiting.</p>
<p>Cheers,<br />
Aidan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marco Rizzetto</title>
		<link>http://aidanlister.com/2009/04/better-error-handling-with-cakephp/comment-page-1/#comment-730</link>
		<dc:creator>Marco Rizzetto</dc:creator>
		<pubDate>Tue, 09 Jun 2009 15:09:13 +0000</pubDate>
		<guid isPermaLink="false">http://aidanlister.com/?p=5#comment-730</guid>
		<description>Hi
This article is very interesting I would ask you  a question:

1) To manage the sql error I use OnError in app_model.php  , PHP error with your function in boostrap.php ,  CakeError with app_error.php.

I think that have all error handling (PHP , CAKEPHP and DB) in one place it can be a better solution ( maybe even all with an ad hoc object ).
Do you have any idea about how do this?

Many Thanks</description>
		<content:encoded><![CDATA[<p>Hi<br />
This article is very interesting I would ask you  a question:</p>
<p>1) To manage the sql error I use OnError in app_model.php  , PHP error with your function in boostrap.php ,  CakeError with app_error.php.</p>
<p>I think that have all error handling (PHP , CAKEPHP and DB) in one place it can be a better solution ( maybe even all with an ad hoc object ).<br />
Do you have any idea about how do this?</p>
<p>Many Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joel Perras</title>
		<link>http://aidanlister.com/2009/04/better-error-handling-with-cakephp/comment-page-1/#comment-581</link>
		<dc:creator>Joel Perras</dc:creator>
		<pubDate>Fri, 24 Apr 2009 13:58:09 +0000</pubDate>
		<guid isPermaLink="false">http://aidanlister.com/?p=5#comment-581</guid>
		<description>Hi Aidan, 

would you mind attaching the above proof of concept to the RFC? It would help us keep things a bit more in sync, rather than spreading stuff out around the net. 

Also, as I&#039;m sure you&#039;re aware, RFCs/tickets with patches (or proof of concepts such as this one) and/or test cases are usually looked at a bit more closely than those without.</description>
		<content:encoded><![CDATA[<p>Hi Aidan, </p>
<p>would you mind attaching the above proof of concept to the RFC? It would help us keep things a bit more in sync, rather than spreading stuff out around the net. </p>
<p>Also, as I&#8217;m sure you&#8217;re aware, RFCs/tickets with patches (or proof of concepts such as this one) and/or test cases are usually looked at a bit more closely than those without.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
