Overriding View Templates For Datatypes

Next topic

Author	Message
Tristan Koen	Friday 23 May 2003 1:20:58 am I have a custom template for an article object that contains an embedded object. When displaying the embedded object using {attribute_view_gui attribute=$node.object.data_map.related_object} all I get is the name of the related object. Ideally, I would like to display a number of the attributes of the related object here. Looking through the forums and howto documents, it appears that some people have had some success by placing an embed_class_XX.tpl file in the design/mySchema/override/templates/content/view directory, but only with an embedded object id in an XML attribute. Looking at the debug output, the default related object output is determined by /design/standard/templates/content/datatype/view/ezobjectrelation.tpl. Anyone have any idea how to override this template for a specific class?
Selmah Maxim	Friday 23 May 2003 3:43:13 am Hi .. u can copy /design/standard/templates/content/datatype/view/ezobjectrelation.tpl to /design/MYDISIGN/templates/content/datatype/view/ezobjectrelation.tpl Let`s say u wanna get foreach class another look from Ezobectrelation, the pass vars to ezobectrelation.tpl : {attribute_view_gui attribute=$node.object.data_map.related_object Classid=7} then is ezobectrelation.tpl : {switch match=$Classid} {case match=7}{class # 7} LALALA {/case} {case match=8}{class # 8} LALALA {/case} . .. {/switch} thats it !
Tristan Koen	Friday 23 May 2003 6:50:50 am Hi Selmah, Thanks for the idea. It would definitely work, but it is a bit of a hack. Surely there must be a mechanism within the ezPublish framework that would do the trick? If there is no such mechanism, then I have to question why bother with related objects? It is far cleaner and more maintainable to place an object reference into an XML text attribute (in my opinion anyway).

Author

Message

Friday 23 May 2003 1:20:58 am

I have a custom template for an article object that contains an embedded object. When displaying the embedded object using
{attribute_view_gui attribute=$node.object.data_map.related_object}
all I get is the name of the related object.
Ideally, I would like to display a number of the attributes of the related object here.

Looking through the forums and howto documents, it appears that some people have had some success by placing an embed_class_XX.tpl file in the design/mySchema/override/templates/content/view directory, but only with an embedded object id in an XML attribute.

Looking at the debug output, the default related object output is determined by /design/standard/templates/content/datatype/view/ezobjectrelation.tpl.

Anyone have any idea how to override this template for a specific class?

Selmah Maxim

Friday 23 May 2003 3:43:13 am

Hi ..

u can copy /design/standard/templates/content/datatype/view/ezobjectrelation.tpl

to
/design/MYDISIGN/templates/content/datatype/view/ezobjectrelation.tpl

Let`s say u wanna get foreach class another look from Ezobectrelation, the pass vars to ezobectrelation.tpl :

{attribute_view_gui attribute=$node.object.data_map.related_object Classid=7}

then is ezobectrelation.tpl :

{switch match=$Classid}
{case match=7}{*class # 7}
LALALA
{/case}
{case match=8}{*class # 8}
LALALA
{/case}
.
..
{/switch}

thats it !

Tristan Koen

Friday 23 May 2003 6:50:50 am

Hi Selmah,

Thanks for the idea. It would definitely work, but it is a bit of a hack. Surely there must be a mechanism within the ezPublish framework that would do the trick?
If there is no such mechanism, then I have to question why bother with related objects? It is far cleaner and more maintainable to place an object reference into an XML text attribute (in my opinion anyway).

eZ debug

Timing:	Jan 18 2025 11:24:51
Script start
Timing:	Jan 18 2025 11:24:51
Module start 'layout'
Timing:	Jan 18 2025 11:24:51
Module start 'content'
Timing:	Jan 18 2025 11:24:52
Module end 'content'
Timing:	Jan 18 2025 11:24:52
Script end

Main resources:

Total runtime	0.7530 sec
Peak memory usage	4,096.0000 KB
Database Queries	57

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0071	588.0313	152.6406
Module start 'layout'	0.0071	0.0031	740.6719	39.4766
Module start 'content'	0.0102	0.7416	780.1484	472.3359
Module end 'content'	0.7517	0.0013	1,252.4844	8.1406
Script end	0.7530		1,260.6250

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0034	0.4484	16	0.0002
Check MTime	0.0014	0.1802	16	0.0001
Mysql Total
Database connection	0.0006	0.0762	1	0.0006
Mysqli_queries	0.7008	93.0608	57	0.0123
Looping result	0.0006	0.0803	55	0.0000
Template Total	0.7142	94.8	2	0.3571
Template load	0.0022	0.2879	2	0.0011
Template processing	0.7120	94.5534	2	0.3560
Template load and register function	0.0003	0.0418	1	0.0003
states
state_id_array	0.0019	0.2559	1	0.0019
state_identifier_array	0.0020	0.2654	2	0.0010
Override
Cache load	0.0018	0.2342	33	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0004	0.0565	2	0.0002
Fetch class attribute name	0.0021	0.2750	3	0.0007
XML
Image XML parsing	0.0002	0.0269	2	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0013	3	0.0000
General
dbfile	0.0007	0.0928	10	0.0001
String conversion	0.0000	0.0012	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
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
4	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
6	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 15 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs