View Modes - Bug or stupidity?

Next topic

Author	Message
Tristan Koen	Wednesday 23 July 2003 7:03:05 am I have encountered some strange behaviour on ez3.1-1 when creating custom view modes. If I create a new view template - say myview.tpl - and copy it across in to my /design/mysite/override/templates/node/view directory, it works perfectly with {node_view_gui view=myview content_node=$Section:item} The problem comes in when I try to restrict the template to a specific class - in my case, folders. My understanding is that the restriction is handled by changing the filename. So in my case I rename the template to myview_class_1.tpl and it should work. For some reason it doesn't and I am getting quite frustrated here. Can anyone shed some light on this problem? Is it a bug or am I just extremely stupid? Regards, Tristan
Michael Bolien	Wednesday 23 July 2003 7:37:02 am Hi Tristan, it's not your stupidy, it's because they change the template override behaviour in 3.1.1. I encountered the same phenomenon. And you have two choices: first you can setup {node_view_gui view=myview_class_1.tpl content_node=$Section:item} this will show your template for all classes or you can use the new override.ini.append in your settings/siteaccess/design-folder. Here you have to enter in the override.ini.append: [myview] Source=node/view/full.tpl MatchFile=myview.tpl Subdir=templates Match[class]=1 in your template you should enter: {node_view_gui view=full content_node=$Section:item} That should do it. Michael
Tristan Koen	Thursday 24 July 2003 12:15:56 am Thanks Michael. Now that I think about it, it does make sense in terms of presenting a consistent override framework. ezTeam: Please would you remove the 'old style' view mode templates from the demo in the next release? I have used the demo as a source of examples for most of my learning curve and this one really caught me out... Regards, Tristan

Author

Message

Wednesday 23 July 2003 7:03:05 am

I have encountered some strange behaviour on ez3.1-1 when creating custom view modes.
If I create a new view template - say myview.tpl - and copy it across in to my /design/mysite/override/templates/node/view directory, it works perfectly with
{node_view_gui view=myview content_node=$Section:item}

The problem comes in when I try to restrict the template to a specific class - in my case, folders. My understanding is that the restriction is handled by changing the filename. So in my case I rename the template to myview_class_1.tpl and it *should* work.

For some reason it doesn't and I am getting quite frustrated here. Can anyone shed some light on this problem? Is it a bug or am I just extremely stupid?

Regards,

Tristan

Michael Bolien

Wednesday 23 July 2003 7:37:02 am

Hi Tristan, it's not your stupidy, it's because they change the template override behaviour in 3.1.1.

I encountered the same phenomenon. And you have two choices: first you can setup
{node_view_gui view=myview_class_1.tpl content_node=$Section:item}
this will show your template for all classes
or
you can use the new override.ini.append in your settings/siteaccess/design-folder. Here you have to enter in the override.ini.append:
[myview]
Source=node/view/full.tpl
MatchFile=myview.tpl
Subdir=templates
Match[class]=1

in your template you should enter:
{node_view_gui view=full content_node=$Section:item}

That should do it.

Michael

Tristan Koen

Thursday 24 July 2003 12:15:56 am

Thanks Michael. Now that I think about it, it does make sense in terms of presenting a consistent override framework.

ezTeam: Please would you remove the 'old style' view mode templates from the demo in the next release? I have used the demo as a source of examples for most of my learning curve and this one really caught me out...

Regards,

Tristan

eZ debug

Timing:	Jan 18 2025 16:03:41
Script start
Timing:	Jan 18 2025 16:03:41
Module start 'layout'
Timing:	Jan 18 2025 16:03:41
Module start 'content'
Timing:	Jan 18 2025 16:03:42
Module end 'content'
Timing:	Jan 18 2025 16:03:42
Script end

Main resources:

Total runtime	0.8414 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.0048	587.9141	152.6250
Module start 'layout'	0.0048	0.0027	740.5391	39.4453
Module start 'content'	0.0075	0.8324	779.9844	471.0781
Module end 'content'	0.8399	0.0014	1,251.0625	12.1641
Script end	0.8413		1,263.2266

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0032	0.3797	16	0.0002
Check MTime	0.0012	0.1464	16	0.0001
Mysql Total
Database connection	0.0006	0.0679	1	0.0006
Mysqli_queries	0.7987	94.9308	57	0.0140
Looping result	0.0004	0.0513	55	0.0000
Template Total	0.8125	96.6	2	0.4062
Template load	0.0022	0.2592	2	0.0011
Template processing	0.8103	96.3081	2	0.4051
Template load and register function	0.0001	0.0132	1	0.0001
states
state_id_array	0.0007	0.0838	1	0.0007
state_identifier_array	0.0011	0.1362	2	0.0006
Override
Cache load	0.0018	0.2175	31	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0008	0.0945	2	0.0004
Fetch class attribute name	0.0009	0.1037	3	0.0003
XML
Image XML parsing	0.0002	0.0237	2	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0008	3	0.0000
General
dbfile	0.0005	0.0643	10	0.0001
String conversion	0.0000	0.0009	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
3	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
5	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: 13 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs