Error handling in eZ publish

Next topic

Author	Message
Kristoffer Brabrand	Friday 18 February 2011 3:40:27 am The error logging feature in eZ publish is a good tool to log errors raised when in production, but when developing it's more a hurdle to get over... Whereas PHP would normally provide you with something like "Fatal error: call to a member function on a non object on line 76", eZ aids the developer by outputting "Fatal error: eZ Publish did not finish its request. The execution of eZ Publish was abruptly ended. Contact website owner with current url and what you did, and owner will be able to debug the issue further." Is there a way to get useful error output, and is there a way to make eZ print it out on the screen instead of logging some and withholding the rest? Any guidance and help would be greatly appreciated.
André R.	Friday 18 February 2011 6:04:28 am If you enable php's display_errors setting and eZ Publish debug output you'll be able to see what is going on. eZ Online Editor 5: http://projects.ez.no/ezoe \|\| eZJSCore (Ajax): http://projects.ez.no/ezjscore \|\| eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom

Author

Message

Friday 18 February 2011 3:40:27 am

The error logging feature in eZ publish is a good tool to log errors raised when in production, but when developing it's more a hurdle to get over... Whereas PHP would normally provide you with something like

"Fatal error: call to a member function on a non object on line 76",

eZ aids the developer by outputting "Fatal error: eZ Publish did not finish its request. The execution of eZ Publish was abruptly ended. Contact website owner with current url and what you did, and owner will be able to debug the issue further."

Is there a way to get useful error output, and is there a way to make eZ print it out on the screen instead of logging some and withholding the rest?

Any guidance and help would be greatly appreciated.

André R.

Friday 18 February 2011 6:04:28 am

If you enable php's display_errors setting and eZ Publish debug output you'll be able to see what is going on.

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

eZ debug

Timing:	Jan 29 2025 14:45:06
Script start
Timing:	Jan 29 2025 14:45:06
Module start 'layout'
Timing:	Jan 29 2025 14:45:06
Module start 'content'
Timing:	Jan 29 2025 14:45:06
Module end 'content'
Timing:	Jan 29 2025 14:45:06
Script end

Main resources:

Total runtime	0.0143 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.0060	588.1328	151.2109
Module start 'layout'	0.0060	0.0021	739.3438	36.6563
Module start 'content'	0.0081	0.0048	776.0000	90.1563
Module end 'content'	0.0129	0.0013	866.1563	29.9766
Script end	0.0143		896.1328

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	16.7965	14	0.0002
Check MTime	0.0011	7.8577	14	0.0001
Mysql Total
Database connection	0.0008	5.5138	1	0.0008
Mysqli_queries	0.0031	21.7047	3	0.0010
Looping result	0.0000	0.0701	1	0.0000
Template Total	0.0010	7.3	1	0.0010
Template load	0.0008	5.7673	1	0.0008
Template processing	0.0002	1.4631	1	0.0002
Override
Cache load	0.0006	4.0506	1	0.0006
General
dbfile	0.0012	8.0746	8	0.0001
String conversion	0.0000	0.0551	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