[3.4beta1] how can I debug templates that get included when calling tool_bar?

Next topic

Author	Message
Chris Fullerton	Thursday 13 May 2004 6:53:57 am I'm playing around with the new toolbar functionality, and have it "mostly" working, but I can't find a way to tell which templates are being included. Inder 3.3.4, I'd change two settings in siteaccess/SITENAME/site.ini.append: [TemplateSettings] Debug=disabled #Debug=enabled [DebugSettings] DebugOutput=disabled #DebugOutput=enabled and each included template would show up. Now, when I add the following to override/site.ini.append: [TemplateSettings] Debug=enabled I get HTML comments that show which templates get included, but it seems to be missing some of them - tool items are wrapped in a <div class=toolbar-item> and I can't find out where that's coming from!
Willie Seabrook	Friday 14 May 2004 11:28:38 pm Hi Chris, Have a look in debug.ini... there might be some more settings in there. You could also do a recursive fgrep from the design folder downwards to find the file with div class=toolbar-item in it. Sometimes with ezPublish I find manual ways on the command line that are far faster. ;-) Regards, Willie
Chris Fullerton	Saturday 15 May 2004 9:04:50 am It turns out this code was coming from a php module, not a template. I filed a bug about it.

Author

Message

Thursday 13 May 2004 6:53:57 am

I'm playing around with the new toolbar functionality, and have it "mostly" working, but I can't find a way to tell which templates are being included.

Inder 3.3.4, I'd change two settings in siteaccess/SITENAME/site.ini.append:

[TemplateSettings]
Debug=disabled
#Debug=enabled

[DebugSettings]
DebugOutput=disabled
#DebugOutput=enabled

and each included template would show up.

Now, when I add the following to override/site.ini.append:

[TemplateSettings]
Debug=enabled

I get HTML comments that show which templates get included, but it seems to be missing some of them - tool items are wrapped in a <div class=toolbar-item> and I can't find out where that's coming from!

Willie Seabrook

Friday 14 May 2004 11:28:38 pm

Hi Chris,

Have a look in debug.ini... there *might* be some more settings in there.

You could also do a recursive fgrep from the design folder downwards to find the file with div class=toolbar-item in it.

Sometimes with ezPublish I find manual ways on the command line that are far faster.

;-)

Regards,
Willie

Chris Fullerton

Saturday 15 May 2004 9:04:50 am

It turns out this code was coming from a php module, not a template. I filed a bug about it.

eZ debug

Timing:	Jan 31 2025 03:38:12
Script start
Timing:	Jan 31 2025 03:38:12
Module start 'layout'
Timing:	Jan 31 2025 03:38:12
Module start 'content'
Timing:	Jan 31 2025 03:38:12
Module end 'content'
Timing:	Jan 31 2025 03:38:12
Script end

Main resources:

Total runtime	0.0205 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0041	588.6250	151.2734
Module start 'layout'	0.0041	0.0030	739.8984	220.7656
Module start 'content'	0.0071	0.0120	960.6641	997.7891
Module end 'content'	0.0191	0.0013	1,958.4531	29.9922
Script end	0.0204		1,988.4453

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0023	11.1662	14	0.0002
Check MTime	0.0010	4.6861	14	0.0001
Mysql Total
Database connection	0.0007	3.5157	1	0.0007
Mysqli_queries	0.0019	9.3523	3	0.0006
Looping result	0.0000	0.0385	1	0.0000
Template Total	0.0009	4.4	1	0.0009
Template load	0.0007	3.6078	1	0.0007
Template processing	0.0002	0.7962	1	0.0002
Override
Cache load	0.0005	2.6158	1	0.0005
General
dbfile	0.0012	5.7305	8	0.0001
String conversion	0.0000	0.0210	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