Error 500 and FatalErrorHandler

Previous topic

Developer

Next topic

Author	Message
Maxime Thomas	Monday 29 March 2010 7:21:00 am Hi, I've tried to make the following thing : - Creating a new extension with one module and one action. - Inside the action, I've put the following code : exit(1); - Defining role and policies. - Accessing the module/action The result is that the HTTP 500 is not handled by eZPublish and an eZFatalError is thrown until the top : <strong>Fatal error</strong>: eZ Publish did not finish its request The execution of eZ Publish was abruptly ended, the debug output is present below. How can I handle that without hacking the kernel (it means declaring a new eZFatalError...) ? The important code is in the index.php. Thank you for answers. Maxime Thomas maxime.thomas@wascou.org \| www.wascou.org \| http://twitter.com/wascou Company Blog : http://www.wascou.org/eng/Company/Blog Technical Blog : http://share.ez.no/blogs/maxime-thomas

Author

Message

Maxime Thomas

Monday 29 March 2010 7:21:00 am

Hi,

I've tried to make the following thing :

- Creating a new extension with one module and one action.

- Inside the action, I've put the following code :

exit(1);

- Defining role and policies.

- Accessing the module/action

The result is that the HTTP 500 is not handled by eZPublish and an eZFatalError is thrown until the top :

<strong>Fatal error</strong>: eZ Publish did not finish its request


The 
execution of eZ Publish was abruptly ended, the debug output is present 
below.

How can I handle that without hacking the kernel (it means declaring a new eZFatalError...) ?

The important code is in the index.php.

Thank you for answers.

Maxime Thomas
maxime.thomas@wascou.org | www.wascou.org | http://twitter.com/wascou

Company Blog : http://www.wascou.org/eng/Company/Blog
Technical Blog : http://share.ez.no/blogs/maxime-thomas

eZ debug

Timing:	Jan 29 2025 23:46:03
Script start
Timing:	Jan 29 2025 23:46:03
Module start 'layout'
Timing:	Jan 29 2025 23:46:03
Module start 'content'
Timing:	Jan 29 2025 23:46:03
Module end 'content'
Timing:	Jan 29 2025 23:46:03
Script end

Main resources:

Total runtime	0.0130 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0053	588.1328	151.2109
Module start 'layout'	0.0053	0.0026	739.3438	36.6484
Module start 'content'	0.0079	0.0040	775.9922	90.1719
Module end 'content'	0.0119	0.0011	866.1641	29.9922
Script end	0.0130		896.1563

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0022	16.5810	14	0.0002
Check MTime	0.0010	7.6632	14	0.0001
Mysql Total
Database connection	0.0009	6.5805	1	0.0009
Mysqli_queries	0.0026	20.3065	3	0.0009
Looping result	0.0000	0.1079	1	0.0000
Template Total	0.0008	6.1	1	0.0008
Template load	0.0006	4.6253	1	0.0006
Template processing	0.0002	1.4119	1	0.0002
Override
Cache load	0.0004	3.2445	1	0.0004
General
dbfile	0.0002	1.8070	8	0.0000
String conversion	0.0000	0.0640	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs