Creating dynamic content

Next topic

Author	Message
Carl Worswick	Wednesday 23 March 2005 3:16:19 pm Having followed through the TSCM tutorial without any problems I now want to get my hands dirty but I've hit on a problem from the outset. I want, like the TSCM, a banner, left menu and footer with some dynamic content in the middle. Creating the banner, menu and footer in the pagelayout.tpl has been no problem but I am a little confused on how the string {$module_result.content} will connect with my dynamic template which I have created in the overrides folder, can anyone clear this up for me? What I don't want is to create an article and point the site.ini.append.php at it. Thanks
Łukasz Serwatka	Tuesday 29 March 2005 1:03:57 am {$module_result.content} Contains information about the result (and the result itself) generated by the module/view that was executed. View templates are mostly associated with the content views. The content view is actually a presentation of the content or page requested by the user throught the URL. For example, mysite.com/content/view/full/2 refers to viewing the content in the full view of node 2. You can create new view for /view/full/2 in Design->Templates->/node/view/full.tpl Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog

Author

Message

Wednesday 23 March 2005 3:16:19 pm

Having followed through the TSCM tutorial without any problems I now want to get my hands dirty but I've hit on a problem from the outset.

I want, like the TSCM, a banner, left menu and footer with some dynamic content in the middle. Creating the banner, menu and footer in the pagelayout.tpl has been no problem but I am a little confused on how the string {$module_result.content} will connect with my dynamic template which I have created in the overrides folder, can anyone clear this up for me?

What I don't want is to create an article and point the site.ini.append.php at it.

Thanks

Łukasz Serwatka

Tuesday 29 March 2005 1:03:57 am

{$module_result.content}

Contains information about the result (and the result itself) generated by the module/view that was executed.

View templates are mostly associated with the content views. The content view is actually a presentation of the content or page requested by the user throught the URL. For example, mysite.com/content/view/full/2 refers to viewing the content in the full view of node 2.

You can create new view for /view/full/2 in Design->Templates->/node/view/full.tpl

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

eZ debug

Timing:	Jan 19 2025 03:22:26
Script start
Timing:	Jan 19 2025 03:22:26
Module start 'layout'
Timing:	Jan 19 2025 03:22:26
Module start 'content'
Timing:	Jan 19 2025 03:22:26
Module end 'content'
Timing:	Jan 19 2025 03:22:26
Script end

Main resources:

Total runtime	0.0142 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.0057	589.1563	152.6250
Module start 'layout'	0.0057	0.0023	741.7813	39.4453
Module start 'content'	0.0080	0.0044	781.2266	89.3516
Module end 'content'	0.0125	0.0017	870.5781	30.3047
Script end	0.0141		900.8828

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	16.6473	14	0.0002
Check MTime	0.0011	7.4860	14	0.0001
Mysql Total
Database connection	0.0006	4.2599	1	0.0006
Mysqli_queries	0.0023	16.0782	3	0.0008
Looping result	0.0000	0.0926	1	0.0000
Template Total	0.0013	9.4	1	0.0013
Template load	0.0007	4.7516	1	0.0007
Template processing	0.0007	4.6320	1	0.0007
Override
Cache load	0.0004	3.1772	1	0.0004
General
dbfile	0.0003	1.9144	8	0.0000
String conversion	0.0000	0.0505	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