Click Node link.....display article with $module_results.content

Next topic

Author	Message
Douglas Johnson	Thursday 24 July 2003 3:29:59 pm How can I display the article within a node? Example...the user clicks on the link to node(folder) 23, this displays the article within that node(folder) using the $module_results.content statement. I had this working, but now somehow since I started over, it no longer works. Again.....the user clicks on the link to node(folder) 23, this displays the article within that node(folder) using the $module_results.content statement. Any ideas? Thanks...Doug Johnson
Bjørn Kaarstein	Thursday 24 July 2003 11:21:24 pm If you're using ezP 3.0, you'll have to write an override for full_class_1.tpl. This is the override that will decide how to display the content of the folder class. Pretty much the same in ezP 3.1, but there you can name you override whatever you want, but you have to add some lines to your override.ini. Something like: [folder_full] Source=node/view/full.tpl MatchFile=folder_full.tpl Subdir=templates Match[class]=1 Also it's pretty useful to turn on debugging in your site.ini.append.php. [TemplateSettings] Debug=enabled This will show you which template(s) are used on your respective node, and is a way to make sure that you are working with the correct file. Regards Bjørn.

Author

Message

Thursday 24 July 2003 3:29:59 pm

How can I display the article within a node? Example...the user clicks on the link to node(folder) 23, this displays the article within that node(folder) using the $module_results.content statement. I had this working, but now somehow since I started over, it no longer works. Again.....the user clicks on the link to node(folder) 23, this displays the article within that node(folder) using the $module_results.content statement. Any ideas?
Thanks...Doug Johnson

Bjørn Kaarstein

Thursday 24 July 2003 11:21:24 pm

If you're using ezP 3.0, you'll have to write an override for full_class_1.tpl. This is the override that will decide how to display the content of the folder class.

Pretty much the same in ezP 3.1, but there you can name you override whatever you want, but you have to add some lines to your override.ini.

Something like:

[folder_full]
Source=node/view/full.tpl
MatchFile=folder_full.tpl
Subdir=templates
Match[class]=1

Also it's pretty useful to turn on debugging in your site.ini.append.php.

[TemplateSettings]
Debug=enabled

This will show you which template(s) are used on your respective node, and is a way to make sure that you are working with the correct file.

Regards Bjørn.

eZ debug

Timing:	Jan 18 2025 19:29:47
Script start
Timing:	Jan 18 2025 19:29:47
Module start 'layout'
Timing:	Jan 18 2025 19:29:47
Module start 'content'
Timing:	Jan 18 2025 19:29:47
Module end 'content'
Timing:	Jan 18 2025 19:29:47
Script end

Main resources:

Total runtime	0.0228 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.0134	588.1719	152.6563
Module start 'layout'	0.0134	0.0021	740.8281	39.5078
Module start 'content'	0.0155	0.0052	780.3359	89.2891
Module end 'content'	0.0207	0.0020	869.6250	30.3047
Script end	0.0227		899.9297

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	11.9230	14	0.0002
Check MTime	0.0011	5.0115	14	0.0001
Mysql Total
Database connection	0.0074	32.5551	1	0.0074
Mysqli_queries	0.0017	7.4737	3	0.0006
Looping result	0.0000	0.0482	1	0.0000
Template Total	0.0017	7.3	1	0.0017
Template load	0.0009	3.8683	1	0.0009
Template processing	0.0008	3.4380	1	0.0008
Override
Cache load	0.0006	2.6120	1	0.0006
General
dbfile	0.0002	1.0689	8	0.0000
String conversion	0.0000	0.0911	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