By default it will show a page like missing something, but showing the fatal error message, with the file and line that it happened. If debug is disabled, it will show internal server error page.
+1 I like it that there will be a build in fatal error handler soon. as of right now one would have to apply some self-coded hack to catch and log those.
I used to do it this way:
register_shutdown_function('shutdownFunction'); function shutDownFunction() { //manual logging }
Am Sonntag, 1. April 2012 02:31:18 UTC+2 schrieb Juan Basso:
> By default it will show a page like missing something, but showing the > fatal error message, with the file and line that it happened. If debug is > disabled, it will show internal server error page.
> What you think?
> Juan Basso
Am Sonntag, 1. April 2012 02:31:18 UTC+2 schrieb Juan Basso:
> By default it will show a page like missing something, but showing the > fatal error message, with the file and line that it happened. If debug is > disabled, it will show internal server error page.
> What you think?
> Juan Basso
Am Sonntag, 1. April 2012 02:31:18 UTC+2 schrieb Juan Basso:
> By default it will show a page like missing something, but showing the > fatal error message, with the file and line that it happened. If debug is > disabled, it will show internal server error page.
By default it will show a page like missing something, but showing the fatal error message, with the file and line that it happened. If debug is disabled, it will show internal server error page.
> By default it will show a page like missing something, but showing the > fatal error message, with the file and line that it happened. If debug is > disabled, it will show internal server error page.
On Sun, Apr 1, 2012 at 1:57 PM, mark_story <mark.st...@gmail.com> wrote: > Great work Juan! I added a few comments to the docs commits. I guess I > should better document the new console handler better as well. :)
> -Mark
> On Saturday, 31 March 2012 20:31:18 UTC-4, Juan Basso wrote:
>> Hi guys,
>> I implemented a new handler to catch fatal errors.
>> By default it will show a page like missing something, but showing the >> fatal error message, with the file and line that it happened. If debug is >> disabled, it will show internal server error page.
After talk with Mark, the code was changed. I removed the Error.fatalErrorHandler from configuration and the regular Error.handler will receive the fatal error codes as well. The handler will define what should be the behavior for this situation.
>>> By default it will show a page like missing something, but showing the >>> fatal error message, with the file and line that it happened. If debug is >>> disabled, it will show internal server error page.
Then recently I again updated it to always use 'error' layout instead of 'default' 3495422ac5<https://github.com/cakephp/cakephp/commit/3495422ac5bde8667becaa1e4af...>. I wanted to get everyone's opinion if this is good or it should be reverted back to using error layout only when rendering "safe" messages in case of repeated errors.
On Monday, April 2, 2012 9:38:38 AM UTC+5:30, Juan Basso wrote:
> After talk with Mark, the code was changed. I removed the > Error.fatalErrorHandler from configuration and the regular Error.handler > will receive the fatal error codes as well. The handler will define what > should be the behavior for this situation.
> Code and doc updated.
> Juan Basso
> On Sun, Apr 1, 2012 at 4:56 PM, Juan Basso <jrba...@gmail.com> wrote:
>> Thanks! As the core.php use the same text, I also updated.
>> Juan Basso
>> On Sun, Apr 1, 2012 at 1:57 PM, mark_story <mark.st...@gmail.com> wrote:
>>> Great work Juan! I added a few comments to the docs commits. I guess I >>> should better document the new console handler better as well. :)
>>> -Mark
>>> On Saturday, 31 March 2012 20:31:18 UTC-4, Juan Basso wrote:
>>>> Hi guys,
>>>> I implemented a new handler to catch fatal errors.
>>>> By default it will show a page like missing something, but showing the >>>> fatal error message, with the file and line that it happened. If debug is >>>> disabled, it will show internal server error page.
Assuming that NotFoundException will render "error" layout with this change in 2.2; it is common for 404 error pages to have menus or footer like this https://github.com/blablba so you have to duplicate code from "default" layout in "error" layout and you end up with same problem in case of repeated errors.
> Then recently I again updated it to always use 'error' layout instead of > 'default' 3495422ac5<https://github.com/cakephp/cakephp/commit/3495422ac5bde8667becaa1e4af...>. > I wanted to get everyone's opinion if this is good or it should be reverted > back to using error layout only when rendering "safe" messages in case of > repeated errors.
> -ADmad
> On Monday, April 2, 2012 9:38:38 AM UTC+5:30, Juan Basso wrote:
>> After talk with Mark, the code was changed. I removed the >> Error.fatalErrorHandler from configuration and the regular Error.handler >> will receive the fatal error codes as well. The handler will define what >> should be the behavior for this situation.
>> Code and doc updated.
>> Juan Basso
>> On Sun, Apr 1, 2012 at 4:56 PM, Juan Basso wrote:
>>> Thanks! As the core.php use the same text, I also updated.
>>> Juan Basso
>>> On Sun, Apr 1, 2012 at 1:57 PM, mark_story wrote:
>>>> Great work Juan! I added a few comments to the docs commits. I guess >>>> I should better document the new console handler better as well. :)
>>>> -Mark
>>>> On Saturday, 31 March 2012 20:31:18 UTC-4, Juan Basso wrote:
>>>>> Hi guys,
>>>>> I implemented a new handler to catch fatal errors.
>>>>> By default it will show a page like missing something, but showing the >>>>> fatal error message, with the file and line that it happened. If debug is >>>>> disabled, it will show internal server error page.
On Wed, Apr 4, 2012 at 4:12 PM, majna <majna...@gmail.com> wrote: > Assuming that NotFoundException will render "error" layout with this > change in 2.2; > it is common for 404 error pages to have menus or footer like this > https://github.com/blablba > so you have to duplicate code from "default" layout in "error" layout and > you end up with same problem in case of repeated errors.
> On Tuesday, April 3, 2012 9:15:25 PM UTC+2, ADmad wrote:
>> Then recently I again updated it to always use 'error' layout instead of >> 'default' 3495422ac5<https://github.com/cakephp/cakephp/commit/3495422ac5bde8667becaa1e4af...>. >> I wanted to get everyone's opinion if this is good or it should be reverted >> back to using error layout only when rendering "safe" messages in case of >> repeated errors.
>> -ADmad
>> On Monday, April 2, 2012 9:38:38 AM UTC+5:30, Juan Basso wrote:
>>> After talk with Mark, the code was changed. I removed the >>> Error.fatalErrorHandler from configuration and the regular Error.handler >>> will receive the fatal error codes as well. The handler will define what >>> should be the behavior for this situation.
>>> Code and doc updated.
>>> Juan Basso
>>> On Sun, Apr 1, 2012 at 4:56 PM, Juan Basso wrote:
>>>> Thanks! As the core.php use the same text, I also updated.
>>>> Juan Basso
>>>> On Sun, Apr 1, 2012 at 1:57 PM, mark_story wrote:
>>>>> Great work Juan! I added a few comments to the docs commits. I guess >>>>> I should better document the new console handler better as well. :)
>>>>> -Mark
>>>>> On Saturday, 31 March 2012 20:31:18 UTC-4, Juan Basso wrote:
>>>>>> Hi guys,
>>>>>> I implemented a new handler to catch fatal errors.
>>>>>> By default it will show a page like missing something, but showing >>>>>> the fatal error message, with the file and line that it happened. If debug >>>>>> is disabled, it will show internal server error page.
>>>>>> What you think?
>>>>>> Juan Basso
-- Renan Gonçalves aka renan.saddam Software Engineer at TrueServer B.V. CakePHP Core Developer Website: renangoncalves dot com Amsterdam, The Netherlands
ADmad: I would think the error layout would only be used for repeat errors or errors encountered when rendering an error. Having it used for all errors means people will put their app helpers into it. This means that repeat errors will continue to fail fatally.
> Then recently I again updated it to always use 'error' layout instead of > 'default' 3495422ac5<https://github.com/cakephp/cakephp/commit/3495422ac5bde8667becaa1e4af...>. > I wanted to get everyone's opinion if this is good or it should be reverted > back to using error layout only when rendering "safe" messages in case of > repeated errors.
> -ADmad
> On Monday, April 2, 2012 9:38:38 AM UTC+5:30, Juan Basso wrote:
>> After talk with Mark, the code was changed. I removed the >> Error.fatalErrorHandler from configuration and the regular Error.handler >> will receive the fatal error codes as well. The handler will define what >> should be the behavior for this situation.
>> Code and doc updated.
>> Juan Basso
>> On Sun, Apr 1, 2012 at 4:56 PM, Juan Basso <jrba...@gmail.com> wrote:
>>> Thanks! As the core.php use the same text, I also updated.
>>> Juan Basso
>>> On Sun, Apr 1, 2012 at 1:57 PM, mark_story <mark.st...@gmail.com> wrote:
>>>> Great work Juan! I added a few comments to the docs commits. I guess >>>> I should better document the new console handler better as well. :)
>>>> -Mark
>>>> On Saturday, 31 March 2012 20:31:18 UTC-4, Juan Basso wrote:
>>>>> Hi guys,
>>>>> I implemented a new handler to catch fatal errors.
>>>>> By default it will show a page like missing something, but showing the >>>>> fatal error message, with the file and line that it happened. If debug is >>>>> disabled, it will show internal server error page.
On Thursday, April 5, 2012 12:10:53 AM UTC+5:30, mark_story wrote:
> ADmad: I would think the error layout would only be used for repeat > errors or errors encountered when rendering an error. Having it used for > all errors means people will put their app helpers into it. This means > that repeat errors will continue to fail fatally.
> -Mark
> On Tuesday, April 3, 2012 3:15:25 PM UTC-4, ADmad wrote:
>> Then recently I again updated it to always use 'error' layout instead of >> 'default' 3495422ac5<https://github.com/cakephp/cakephp/commit/3495422ac5bde8667becaa1e4af...>. >> I wanted to get everyone's opinion if this is good or it should be reverted >> back to using error layout only when rendering "safe" messages in case of >> repeated errors.
>> -ADmad
>> On Monday, April 2, 2012 9:38:38 AM UTC+5:30, Juan Basso wrote:
>>> After talk with Mark, the code was changed. I removed the >>> Error.fatalErrorHandler from configuration and the regular Error.handler >>> will receive the fatal error codes as well. The handler will define what >>> should be the behavior for this situation.
>>> Code and doc updated.
>>> Juan Basso
>>> On Sun, Apr 1, 2012 at 4:56 PM, Juan Basso <jrba...@gmail.com> wrote:
>>>> Thanks! As the core.php use the same text, I also updated.
>>>> Juan Basso
>>>> On Sun, Apr 1, 2012 at 1:57 PM, mark_story <mark.st...@gmail.com>wrote:
>>>>> Great work Juan! I added a few comments to the docs commits. I guess >>>>> I should better document the new console handler better as well. :)
>>>>> -Mark
>>>>> On Saturday, 31 March 2012 20:31:18 UTC-4, Juan Basso wrote:
>>>>>> Hi guys,
>>>>>> I implemented a new handler to catch fatal errors.
>>>>>> By default it will show a page like missing something, but showing >>>>>> the fatal error message, with the file and line that it happened. If debug >>>>>> is disabled, it will show internal server error page.
when BadHelper produces fatal, the default layout will cause another error when calling method on non-object GoodHelper, which will hide the original fatal error. In the stack trace only i can see the FatalError handler is starting point, not what the original fatal error was. quick fix was adding $this->layout = 'error'; to the fatal_error.ctp view
Op donderdag 5 april 2012 21:13:07 UTC+2 schreef ADmad het volgende:
> Ok guys I will revert the change and use error layout only in > ExceptionRenderer::_outputMessageSafe() as i had initially done.
> -ADmad
> On Thursday, April 5, 2012 12:10:53 AM UTC+5:30, mark_story wrote:
>> ADmad: I would think the error layout would only be used for repeat >> errors or errors encountered when rendering an error. Having it used for >> all errors means people will put their app helpers into it. This means >> that repeat errors will continue to fail fatally.
>> -Mark
>> On Tuesday, April 3, 2012 3:15:25 PM UTC-4, ADmad wrote:
>>> Then recently I again updated it to always use 'error' layout instead of >>> 'default' 3495422ac5<https://github.com/cakephp/cakephp/commit/3495422ac5bde8667becaa1e4af...>. >>> I wanted to get everyone's opinion if this is good or it should be reverted >>> back to using error layout only when rendering "safe" messages in case of >>> repeated errors.
>>> -ADmad
>>> On Monday, April 2, 2012 9:38:38 AM UTC+5:30, Juan Basso wrote:
>>>> After talk with Mark, the code was changed. I removed the >>>> Error.fatalErrorHandler from configuration and the regular Error.handler >>>> will receive the fatal error codes as well. The handler will define what >>>> should be the behavior for this situation.
>>>> Code and doc updated.
>>>> Juan Basso
>>>> On Sun, Apr 1, 2012 at 4:56 PM, Juan Basso <jrba...@gmail.com> wrote:
>>>>> Thanks! As the core.php use the same text, I also updated.
>>>>> Juan Basso
>>>>> On Sun, Apr 1, 2012 at 1:57 PM, mark_story <mark.st...@gmail.com>wrote:
>>>>>> Great work Juan! I added a few comments to the docs commits. I >>>>>> guess I should better document the new console handler better as well. :)
>>>>>> -Mark
>>>>>> On Saturday, 31 March 2012 20:31:18 UTC-4, Juan Basso wrote:
>>>>>>> Hi guys,
>>>>>>> I implemented a new handler to catch fatal errors.
>>>>>>> By default it will show a page like missing something, but showing >>>>>>> the fatal error message, with the file and line that it happened. If debug >>>>>>> is disabled, it will show internal server error page.
On Friday, 20 April 2012 03:50:31 UTC-4, Ceeram wrote:
> Fatal errors should also use error layout.
> $helpers = array('Good', 'Bad');
> when BadHelper produces fatal, the default layout will cause another error > when calling method on non-object GoodHelper, which will hide the original > fatal error. In the stack trace only i can see the FatalError handler is > starting point, not what the original fatal error was. quick fix was adding > $this->layout = 'error'; to the fatal_error.ctp view
> Op donderdag 5 april 2012 21:13:07 UTC+2 schreef ADmad het volgende:
>> Ok guys I will revert the change and use error layout only in >> ExceptionRenderer::_outputMessageSafe() as i had initially done.
>> -ADmad
>> On Thursday, April 5, 2012 12:10:53 AM UTC+5:30, mark_story wrote:
>>> ADmad: I would think the error layout would only be used for repeat >>> errors or errors encountered when rendering an error. Having it used for >>> all errors means people will put their app helpers into it. This means >>> that repeat errors will continue to fail fatally.
>>> -Mark
>>> On Tuesday, April 3, 2012 3:15:25 PM UTC-4, ADmad wrote:
>>>> Then recently I again updated it to always use 'error' layout instead >>>> of 'default' 3495422ac5<https://github.com/cakephp/cakephp/commit/3495422ac5bde8667becaa1e4af...>. >>>> I wanted to get everyone's opinion if this is good or it should be reverted >>>> back to using error layout only when rendering "safe" messages in case of >>>> repeated errors.
>>>> -ADmad
>>>> On Monday, April 2, 2012 9:38:38 AM UTC+5:30, Juan Basso wrote:
>>>>> After talk with Mark, the code was changed. I removed the >>>>> Error.fatalErrorHandler from configuration and the regular Error.handler >>>>> will receive the fatal error codes as well. The handler will define what >>>>> should be the behavior for this situation.
>>>>> Code and doc updated.
>>>>> Juan Basso
>>>>> On Sun, Apr 1, 2012 at 4:56 PM, Juan Basso <jrba...@gmail.com> wrote:
>>>>>> Thanks! As the core.php use the same text, I also updated.
>>>>>> Juan Basso
>>>>>> On Sun, Apr 1, 2012 at 1:57 PM, mark_story <mark.st...@gmail.com>wrote:
>>>>>>> Great work Juan! I added a few comments to the docs commits. I >>>>>>> guess I should better document the new console handler better as well. :)
>>>>>>> -Mark
>>>>>>> On Saturday, 31 March 2012 20:31:18 UTC-4, Juan Basso wrote:
>>>>>>>> Hi guys,
>>>>>>>> I implemented a new handler to catch fatal errors.
>>>>>>>> By default it will show a page like missing something, but showing >>>>>>>> the fatal error message, with the file and line that it happened. If debug >>>>>>>> is disabled, it will show internal server error page.
> Sounds like a good idea, do you want to make that change Ceeram?
> -Mark
> On Friday, 20 April 2012 03:50:31 UTC-4, Ceeram wrote:
>> Fatal errors should also use error layout.
>> $helpers = array('Good', 'Bad');
>> when BadHelper produces fatal, the default layout will cause another >> error when calling method on non-object GoodHelper, which will hide the >> original fatal error. In the stack trace only i can see the FatalError >> handler is starting point, not what the original fatal error was. quick fix >> was adding $this->layout = 'error'; to the fatal_error.ctp view
>> Op donderdag 5 april 2012 21:13:07 UTC+2 schreef ADmad het volgende:
>>> Ok guys I will revert the change and use error layout only in >>> ExceptionRenderer::_**outputMessageSafe() as i had initially done.
>>> -ADmad
>>> On Thursday, April 5, 2012 12:10:53 AM UTC+5:30, mark_story wrote:
>>>> ADmad: I would think the error layout would only be used for repeat >>>> errors or errors encountered when rendering an error. Having it used for >>>> all errors means people will put their app helpers into it. This means >>>> that repeat errors will continue to fail fatally.
>>>> -Mark
>>>> On Tuesday, April 3, 2012 3:15:25 PM UTC-4, ADmad wrote:
>>>>> Then recently I again updated it to always use 'error' layout instead >>>>> of 'default' 3495422ac5<https://github.com/cakephp/cakephp/commit/3495422ac5bde8667becaa1e4af...>. >>>>> I wanted to get everyone's opinion if this is good or it should be reverted >>>>> back to using error layout only when rendering "safe" messages in case of >>>>> repeated errors.
>>>>> -ADmad
>>>>> On Monday, April 2, 2012 9:38:38 AM UTC+5:30, Juan Basso wrote:
>>>>>> After talk with Mark, the code was changed. I removed the >>>>>> Error.fatalErrorHandler from configuration and the regular Error.handler >>>>>> will receive the fatal error codes as well. The handler will define what >>>>>> should be the behavior for this situation.
>>>>>> Code and doc updated.
>>>>>> Juan Basso
>>>>>> On Sun, Apr 1, 2012 at 4:56 PM, Juan Basso <jrba...@gmail.com> wrote:
>>>>>>> Thanks! As the core.php use the same text, I also updated.
>>>>>>> Juan Basso
>>>>>>> On Sun, Apr 1, 2012 at 1:57 PM, mark_story <mark.st...@gmail.com>wrote:
>>>>>>>> Great work Juan! I added a few comments to the docs commits. I >>>>>>>> guess I should better document the new console handler better as well. :)
>>>>>>>> -Mark
>>>>>>>> On Saturday, 31 March 2012 20:31:18 UTC-4, Juan Basso wrote:
>>>>>>>>> Hi guys,
>>>>>>>>> I implemented a new handler to catch fatal errors.
>>>>>>>>> By default it will show a page like missing something, but showing >>>>>>>>> the fatal error message, with the file and line that it happened. If debug >>>>>>>>> is disabled, it will show internal server error page.
> Sure, setting layout in the view file is ok? > Op 21 apr. 2012 03:18 schreef "mark_story" <mark.st...@gmail.com> het > volgende:
>> Sounds like a good idea, do you want to make that change Ceeram?
>> -Mark
>> On Friday, 20 April 2012 03:50:31 UTC-4, Ceeram wrote:
>>> Fatal errors should also use error layout.
>>> $helpers = array('Good', 'Bad');
>>> when BadHelper produces fatal, the default layout will cause another >>> error when calling method on non-object GoodHelper, which will hide the >>> original fatal error. In the stack trace only i can see the FatalError >>> handler is starting point, not what the original fatal error was. quick fix >>> was adding $this->layout = 'error'; to the fatal_error.ctp view
>>> Op donderdag 5 april 2012 21:13:07 UTC+2 schreef ADmad het volgende:
>>>> Ok guys I will revert the change and use error layout only in >>>> ExceptionRenderer::_**outputMessageSafe() as i had initially done.
>>>> -ADmad
>>>> On Thursday, April 5, 2012 12:10:53 AM UTC+5:30, mark_story wrote:
>>>>> ADmad: I would think the error layout would only be used for repeat >>>>> errors or errors encountered when rendering an error. Having it used for >>>>> all errors means people will put their app helpers into it. This means >>>>> that repeat errors will continue to fail fatally.
>>>>> -Mark
>>>>> On Tuesday, April 3, 2012 3:15:25 PM UTC-4, ADmad wrote:
>>>>>> Then recently I again updated it to always use 'error' layout instead >>>>>> of 'default' 3495422ac5<https://github.com/cakephp/cakephp/commit/3495422ac5bde8667becaa1e4af...>. >>>>>> I wanted to get everyone's opinion if this is good or it should be reverted >>>>>> back to using error layout only when rendering "safe" messages in case of >>>>>> repeated errors.
>>>>>> -ADmad
>>>>>> On Monday, April 2, 2012 9:38:38 AM UTC+5:30, Juan Basso wrote:
>>>>>>> After talk with Mark, the code was changed. I removed the >>>>>>> Error.fatalErrorHandler from configuration and the regular Error.handler >>>>>>> will receive the fatal error codes as well. The handler will define what >>>>>>> should be the behavior for this situation.
>>>>>>> Code and doc updated.
>>>>>>> Juan Basso
>>>>>>> On Sun, Apr 1, 2012 at 4:56 PM, Juan Basso <jrba...@gmail.com>wrote:
>>>>>>>> Thanks! As the core.php use the same text, I also updated.
>>>>>>>> Juan Basso
>>>>>>>> On Sun, Apr 1, 2012 at 1:57 PM, mark_story <mark.st...@gmail.com>wrote:
>>>>>>>>> Great work Juan! I added a few comments to the docs commits. I >>>>>>>>> guess I should better document the new console handler better as well. :)
>>>>>>>>> -Mark
>>>>>>>>> On Saturday, 31 March 2012 20:31:18 UTC-4, Juan Basso wrote:
>>>>>>>>>> Hi guys,
>>>>>>>>>> I implemented a new handler to catch fatal errors.
>>>>>>>>>> By default it will show a page like missing something, but >>>>>>>>>> showing the fatal error message, with the file and line that it happened. >>>>>>>>>> If debug is disabled, it will show internal server error page.
On Saturday, April 21, 2012 9:34:20 PM UTC+5:30, Ceeram wrote:
> After looking again, i see error layout is in app dir only, perhaps fatal > error even use no layout to avoid other issues?
> Op zaterdag 21 april 2012 10:58:48 UTC+2 schreef Ceeram het volgende:
>> Sure, setting layout in the view file is ok? >> Op 21 apr. 2012 03:18 schreef "mark_story" <mark.st...@gmail.com> het >> volgende:
>>> Sounds like a good idea, do you want to make that change Ceeram?
>>> -Mark
>>> On Friday, 20 April 2012 03:50:31 UTC-4, Ceeram wrote:
>>>> Fatal errors should also use error layout.
>>>> $helpers = array('Good', 'Bad');
>>>> when BadHelper produces fatal, the default layout will cause another >>>> error when calling method on non-object GoodHelper, which will hide the >>>> original fatal error. In the stack trace only i can see the FatalError >>>> handler is starting point, not what the original fatal error was. quick fix >>>> was adding $this->layout = 'error'; to the fatal_error.ctp view
>>>> Op donderdag 5 april 2012 21:13:07 UTC+2 schreef ADmad het volgende:
>>>>> Ok guys I will revert the change and use error layout only in >>>>> ExceptionRenderer::_**outputMessageSafe() as i had initially done.
>>>>> -ADmad
>>>>> On Thursday, April 5, 2012 12:10:53 AM UTC+5:30, mark_story wrote:
>>>>>> ADmad: I would think the error layout would only be used for repeat >>>>>> errors or errors encountered when rendering an error. Having it used for >>>>>> all errors means people will put their app helpers into it. This means >>>>>> that repeat errors will continue to fail fatally.
>>>>>> -Mark
>>>>>> On Tuesday, April 3, 2012 3:15:25 PM UTC-4, ADmad wrote:
>>>>>>> Then recently I again updated it to always use 'error' layout >>>>>>> instead of 'default' 3495422ac5<https://github.com/cakephp/cakephp/commit/3495422ac5bde8667becaa1e4af...>. >>>>>>> I wanted to get everyone's opinion if this is good or it should be reverted >>>>>>> back to using error layout only when rendering "safe" messages in case of >>>>>>> repeated errors.
>>>>>>> -ADmad
>>>>>>> On Monday, April 2, 2012 9:38:38 AM UTC+5:30, Juan Basso wrote:
>>>>>>>> After talk with Mark, the code was changed. I removed the >>>>>>>> Error.fatalErrorHandler from configuration and the regular Error.handler >>>>>>>> will receive the fatal error codes as well. The handler will define what >>>>>>>> should be the behavior for this situation.
>>>>>>>> Code and doc updated.
>>>>>>>> Juan Basso
>>>>>>>> On Sun, Apr 1, 2012 at 4:56 PM, Juan Basso <jrba...@gmail.com>wrote:
>>>>>>>>> Thanks! As the core.php use the same text, I also updated.
>>>>>>>>> Juan Basso
>>>>>>>>> On Sun, Apr 1, 2012 at 1:57 PM, mark_story <mark.st...@gmail.com>wrote:
>>>>>>>>>> Great work Juan! I added a few comments to the docs commits. I >>>>>>>>>> guess I should better document the new console handler better as well. :)
>>>>>>>>>> -Mark
>>>>>>>>>> On Saturday, 31 March 2012 20:31:18 UTC-4, Juan Basso wrote:
>>>>>>>>>>> Hi guys,
>>>>>>>>>>> I implemented a new handler to catch fatal errors.
>>>>>>>>>>> By default it will show a page like missing something, but >>>>>>>>>>> showing the fatal error message, with the file and line that it happened. >>>>>>>>>>> If debug is disabled, it will show internal server error page.
