Catching the Exceptions

Next topic

Author	Message
Tihomir Dmitrovic	Thursday 18 August 2011 1:19:30 am Hi, I want to be able to catch exceptions thrown from my extension. It can be thrown from module or from template operator methods. There are 2 main reasons I want to do that. 1. I want to log exceptions with their stacktrace (chained exceptions too) 2. If it is some non critical exceptions (e.g NotEnoughCreditsException), I would like to redirect user to particular page (e.g /buy-credits) I could not find appropriate documentation section which describes the matter. I'm new to ez (but I have 10 years expiriance in php and java web development). Thanks
André R.	Friday 19 August 2011 3:06:25 am Only way would be to have a try block inside your module php code and then dispatch the action you would like to execute. There is no way to catch eZ Publish exceptions at root, so the template involved would have to be executed from your own module. Note: exceptions/redirections in templates is not recommend when inside view cache for instance. 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

Thursday 18 August 2011 1:19:30 am

Hi,

I want to be able to catch exceptions thrown from my extension. It can be thrown from module or from template operator methods.

There are 2 main reasons I want to do that.

1. I want to log exceptions with their stacktrace (chained exceptions too)

2. If it is some non critical exceptions (e.g NotEnoughCreditsException), I would like to redirect user to particular page (e.g /buy-credits)

I could not find appropriate documentation section which describes the matter. I'm new to ez (but I have 10 years expiriance in php and java web development).

Thanks

André R.

Friday 19 August 2011 3:06:25 am

Only way would be to have a try block inside your module php code and then dispatch the action you would like to execute.
There is no way to catch eZ Publish exceptions at root, so the template involved would have to be executed from your own module. Note: exceptions/redirections in templates is not recommend when inside view cache for instance.

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 13:44:52
Script start
Timing:	Jan 29 2025 13:44:52
Module start 'layout'
Timing:	Jan 29 2025 13:44:52
Module start 'content'
Timing:	Jan 29 2025 13:44:52
Module end 'content'
Timing:	Jan 29 2025 13:44:52
Script end

Main resources:

Total runtime	0.0118 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.0050	588.1250	151.2109
Module start 'layout'	0.0050	0.0018	739.3359	36.6563
Module start 'content'	0.0068	0.0037	775.9922	90.1406
Module end 'content'	0.0106	0.0012	866.1328	29.9766
Script end	0.0118		896.1094

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0021	18.1822	14	0.0002
Check MTime	0.0010	8.3645	14	0.0001
Mysql Total
Database connection	0.0009	7.9749	1	0.0009
Mysqli_queries	0.0020	16.5755	3	0.0007
Looping result	0.0000	0.0767	1	0.0000
Template Total	0.0010	8.1	1	0.0010
Template load	0.0007	6.1381	1	0.0007
Template processing	0.0002	1.9296	1	0.0002
Override
Cache load	0.0005	4.0470	1	0.0005
General
dbfile	0.0002	1.8105	8	0.0000
String conversion	0.0000	0.1635	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