admin interface: setting match conditions for an override

Next topic

Author	Message
Greg McAvoy-Jensen	Wednesday 08 February 2006 9:02:08 pm If I have a new override to be used for a portion of the node tree, how to I set the match conditions (or whatever) for that template using the administration interface? I've seen how it is done manually, but I can't find it in 3.7.3's administration interface. Thank you. Granite Horizon, Certified Developer of eZ Publish Web Solutions Provider of the SaaS Solution Granite Horizon In The Cloud \| http://granitehorizon.com/cloud http://granitehorizon.com \| +1 916 647 6350 \| California USA \| @granitegreg Blog: http://granitehorizon.com/blog
Steph A	Saturday 11 February 2006 11:06:41 am You mean like for pagelayout.tpl? Then you should edit the override.ini.append template. Define your nodes in a section - and then just set the match conditions for your template to your section ID.

Author

Message

Wednesday 08 February 2006 9:02:08 pm

If I have a new override to be used for a portion of the node tree, how to I set the match conditions (or whatever) for that template using the administration interface? I've seen how it is done manually, but I can't find it in 3.7.3's administration interface. Thank you.

Granite Horizon, Certified Developer of eZ Publish Web Solutions
Provider of the SaaS Solution Granite Horizon In The Cloud | http://granitehorizon.com/cloud
http://granitehorizon.com | +1 916 647 6350 | California USA | @granitegreg
Blog: http://granitehorizon.com/blog

Steph A

Saturday 11 February 2006 11:06:41 am

You mean like for pagelayout.tpl?
Then you should edit the override.ini.append template. Define your nodes in a section - and then just set the match conditions for your template to your section ID.

eZ debug

Timing:	Jan 18 2025 16:16:51
Script start
Timing:	Jan 18 2025 16:16:51
Module start 'layout'
Timing:	Jan 18 2025 16:16:51
Module start 'content'
Timing:	Jan 18 2025 16:16:51
Module end 'content'
Timing:	Jan 18 2025 16:16:51
Script end

Main resources:

Total runtime	0.0170 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.0068	589.2891	152.6563
Module start 'layout'	0.0068	0.0032	741.9453	39.5078
Module start 'content'	0.0100	0.0050	781.4531	89.3984
Module end 'content'	0.0150	0.0020	870.8516	30.3047
Script end	0.0170		901.1563

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	15.7167	14	0.0002
Check MTime	0.0012	6.9376	14	0.0001
Mysql Total
Database connection	0.0008	4.6465	1	0.0008
Mysqli_queries	0.0030	17.7151	3	0.0010
Looping result	0.0000	0.1120	1	0.0000
Template Total	0.0017	10.0	1	0.0017
Template load	0.0009	5.0401	1	0.0009
Template processing	0.0008	4.9042	1	0.0008
Override
Cache load	0.0006	3.6060	1	0.0006
General
dbfile	0.0003	1.6791	8	0.0000
String conversion	0.0000	0.1779	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.0002 secs