Module Pagelayout

Next topic

Author	Message
Håkan Bergman	Tuesday 18 May 2010 5:05:45 am Hello, I have made an extension that calls a template file and it works correctly. I am using colorbox to call my extension like this: /extension/node_id. The colorbox works fine and the template is loading, but I just want the template to load, not the pagelayout itself. I tried to search for it and also looked at kernel/content/view.php but didn't really see how I could affect the pagelayout. First I tried an override in /siteaccess/page_site in override.ini.append.php with this: [extension_name] Source=pagelayout.tpl MatchFile=extension_name_pagelayout.tpl Subdir=templates That code killed the main pagelayout, so I thought I could move it to /extensions/extension_name/settings/override.ini.append.php. But I got the same default behaviour, ie an empty pagelayout on default main site. I need a hint to where I can find more information about how to manipulate pagelayouts inside the PHP-code.
Gaetano Giunta	Tuesday 18 May 2010 5:17:10 am The override you set up is used globally, as there is no 'criteria' that tells eZ when it has to be applied. If you want to change the pagelayout used in an ezp module/view, you can use the override conditions defined here: http://ez.no/doc/ez_publish/technical_manual/4_x/reference/template_override_conditions If it's a custom view, you can define the pagelayout used in $Results, eg: $Result['pagelayout'] = 'xml_pagelayout.tpl'; Principal Consultant International Business Member of the Community Project Board
Håkan Bergman	Tuesday 18 May 2010 9:23:13 am Hi Gaetano, Thanks for your information. As I want a custom pagelayout (stripped to my needs for a custom JS-box) then $Result['pagelayout'] = 'template.tpl' did the trick. Thanks a lot. I didn't find any information about $Result[] and when I looked in other files all I found was $Result['content'] to load the template I needed.

Author

Message

Tuesday 18 May 2010 5:05:45 am

Hello,

I have made an extension that calls a template file and it works correctly. I am using colorbox to call my extension like this: /extension/node_id. The colorbox works fine and the template is loading, but I just want the template to load, not the pagelayout itself.

I tried to search for it and also looked at kernel/content/view.php but didn't really see how I could affect the pagelayout. First I tried an override in /siteaccess/page_site in override.ini.append.php with this:

[extension_name]

Source=pagelayout.tpl

MatchFile=extension_name_pagelayout.tpl

Subdir=templates

That code killed the main pagelayout, so I thought I could move it to /extensions/extension_name/settings/override.ini.append.php. But I got the same default behaviour, ie an empty pagelayout on default main site. I need a hint to where I can find more information about how to manipulate pagelayouts inside the PHP-code.

Gaetano Giunta

Tuesday 18 May 2010 5:17:10 am

The override you set up is used globally, as there is no 'criteria' that tells eZ when it has to be applied.

If you want to change the pagelayout used in an ezp module/view, you can use the override conditions defined here: http://ez.no/doc/ez_publish/technical_manual/4_x/reference/template_override_conditions

If it's a custom view, you can define the pagelayout used in $Results, eg:

$Result['pagelayout'] = 'xml_pagelayout.tpl';

Principal Consultant International Business
Member of the Community Project Board

Håkan Bergman

Tuesday 18 May 2010 9:23:13 am

Hi Gaetano,

Thanks for your information.

As I want a custom pagelayout (stripped to my needs for a custom JS-box) then $Result['pagelayout'] = 'template.tpl' did the trick. Thanks a lot. I didn't find any information about $Result[] and when I looked in other files all I found was $Result['content'] to load the template I needed.

eZ debug

Timing:	Jan 30 2025 19:52:34
Script start
Timing:	Jan 30 2025 19:52:34
Module start 'layout'
Timing:	Jan 30 2025 19:52:34
Module start 'content'
Timing:	Jan 30 2025 19:52:34
Module end 'content'
Timing:	Jan 30 2025 19:52:34
Script end

Main resources:

Total runtime	0.0489 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0095	588.0156	151.1953
Module start 'layout'	0.0095	0.0045	739.2109	220.6719
Module start 'content'	0.0139	0.0334	959.8828	997.6797
Module end 'content'	0.0474	0.0015	1,957.5625	33.9922
Script end	0.0489		1,991.5547

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0028	5.7315	14	0.0002
Check MTime	0.0011	2.2032	14	0.0001
Mysql Total
Database connection	0.0016	3.2252	1	0.0016
Mysqli_queries	0.0056	11.3997	3	0.0019
Looping result	0.0000	0.0244	1	0.0000
Template Total	0.0011	2.2	1	0.0011
Template load	0.0009	1.7949	1	0.0009
Template processing	0.0002	0.4396	1	0.0002
Override
Cache load	0.0006	1.2490	1	0.0006
General
dbfile	0.0190	38.7553	8	0.0024
String conversion	0.0000	0.0141	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