RH Column

Next topic

Author	Message
Tristan Koen	Monday 28 July 2003 5:29:08 am Hi All, What is the best approach to building a RH column - similar to the one on the http://ez.no website? THe RH column would contain items such as - search - login - user registration - mail article to friend - related items - etc. It cannot be part of the pagelayout template since different parts of the website will have different items in the RH column. Can anyone give some advice on the best way to achieve this? My current thinking is that it should be part of $module_result.content. The drawback is that a lot of code is repeated in the various templates which makes maintenance a bit more tricky (eg. if I were to move the search function out of the RH column in the the page header I would have to modify every single pagelayout template). There must be a better way... Regards, Tristan
Bjørn Kaarstein	Monday 28 July 2003 6:18:01 am You might try to use {section show} or {switch/case} statements in your pagelayout. In that way, you have it all in one place and maintenance will be easy. I don't know whether this is the best way, or even possible in your case, but it's a suggestion. Regards Bjørn

Author

Message

Monday 28 July 2003 5:29:08 am

Hi All,

What is the best approach to building a RH column - similar to the one on the http://ez.no website?
THe RH column would contain items such as
- search
- login
- user registration
- mail article to friend
- related items
- etc.
It cannot be part of the pagelayout template since different parts of the website will have different items in the RH column.
Can anyone give some advice on the best way to achieve this?

My current thinking is that it should be part of $module_result.content. The drawback is that a lot of code is repeated in the various templates which makes maintenance a bit more tricky (eg. if I were to move the search function out of the RH column in the the page header I would have to modify every single pagelayout template).

There must be a better way...

Regards,

Tristan

Bjørn Kaarstein

Monday 28 July 2003 6:18:01 am

You might try to use {section show} or {switch/case} statements in your pagelayout. In that way, you have it all in one place and maintenance will be easy.

I don't know whether this is the best way, or even possible in your case, but it's a suggestion.

Regards Bjørn

eZ debug

Timing:	Jan 31 2025 04:27:50
Script start
Timing:	Jan 31 2025 04:27:50
Module start 'layout'
Timing:	Jan 31 2025 04:27:50
Module start 'content'
Timing:	Jan 31 2025 04:27:50
Module end 'content'
Timing:	Jan 31 2025 04:27:50
Script end

Main resources:

Total runtime	0.0144 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.0052	588.0078	151.1953
Module start 'layout'	0.0052	0.0025	739.2031	36.6016
Module start 'content'	0.0077	0.0051	775.8047	90.0000
Module end 'content'	0.0128	0.0016	865.8047	29.9922
Script end	0.0144		895.7969

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	16.4717	14	0.0002
Check MTime	0.0011	7.4844	14	0.0001
Mysql Total
Database connection	0.0007	4.9692	1	0.0007
Mysqli_queries	0.0026	17.7906	3	0.0009
Looping result	0.0000	0.0679	1	0.0000
Template Total	0.0012	8.2	1	0.0012
Template load	0.0009	6.5118	1	0.0009
Template processing	0.0002	1.6603	1	0.0002
Override
Cache load	0.0006	4.0231	1	0.0006
General
dbfile	0.0003	2.0712	8	0.0000
String conversion	0.0000	0.0431	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