setting "match conditions" on an override template in admin

«

Previous topic

|

|

Next topic

»

Author	Message
Greg McAvoy-Jensen	Tuesday 21 February 2006 10:06:44 pm How does one set the "match conditions" on an override template using the administration interface? I'm using 3.7.3. I used to know where to find this function, but in recent versions it seems to have disappeared. Thanks! 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
Greg McAvoy-Jensen	Friday 03 March 2006 10:02:48 pm Ok, now I get it. You just have to edit this template: /node/view/full.tpl. Then you can set match conditions. 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
Christopher Grondahl	Saturday 04 March 2006 3:54:29 pm I have a similar questions regarding the pagelayout.tpl - how can I access it's match conditions? I would like to assign pagelayout-overrides to specific sections, but can't seem to make it work. Chris ez site: http://www.acem.no Every day is Groundhog Day
Felix Laate	Sunday 05 March 2006 2:29:00 am Hi, just make an override and use a criteria like this Match[section]=_ID_OF THE_SECTION_ in your override.ini Felix PS! Don't forget the permissions! Publlic Relations Manager Greater Stavanger www.greaterstavanger.com

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 18 2025 11:30:11
Script start
Timing:	Jan 18 2025 11:30:11
Module start 'layout'
Timing:	Jan 18 2025 11:30:11
Module start 'content'
Timing:	Jan 18 2025 11:30:11
Module end 'content'
Timing:	Jan 18 2025 11:30:11
Script end

Main resources:

Total runtime	0.0176 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.0071	589.3047	152.6563
Module start 'layout'	0.0071	0.0029	741.9609	39.5078
Module start 'content'	0.0100	0.0054	781.4688	93.4297
Module end 'content'	0.0154	0.0022	874.8984	34.3047
Script end	0.0175		909.2031

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	14.9797	14	0.0002
Check MTime	0.0012	6.7928	14	0.0001
Mysql Total
Database connection	0.0011	6.3480	1	0.0011
Mysqli_queries	0.0034	19.4345	3	0.0011
Looping result	0.0000	0.0963	1	0.0000
Template Total	0.0017	9.7	1	0.0017
Template load	0.0009	5.3634	1	0.0009
Template processing	0.0008	4.2772	1	0.0008
Override
Cache load	0.0007	3.6981	1	0.0007
General
dbfile	0.0002	1.2205	8	0.0000
String conversion	0.0000	0.0461	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