How to Override modules pagelayout

Next topic

Author	Message
Pierre Tissot	Monday 30 July 2007 7:31:34 am Hi, I have a site that need to present the shop and advance search with a different looks (each one with their own layout) than the default pagelayout. Since they are modules and not nodes or classes I don't know how to make it. I try two approaches: - I try the layout/set/(mypage_layout) but all the futher links of this pagelayout built with ezurl are reflecting the /layout/set/(mypage_layout). - I check the sections match criteria, but we cannot associate a section to a module, so I don't have idea of how I can use this. Are they other strategies? because none of those ones are suitable for me? Thanks PiR
Bruce Morrison	Monday 30 July 2007 5:00:00 pm Hi Pierre I've had a look at the source for content/advancedsearch (kernel/content/advancedsearch.php) and it appears that you will only beable to override based on the section. if ( $searchSectionID != -1 ) { include_once( 'kernel/common/eztemplatedesignresource.php' ); $res =& eZTemplateDesignResource::instance(); $res->setKeys( array( array( 'section', $searchSectionID ) ) ); } It appears that $searchSectionID can be set in the search form. I'm unsure if this effects the actual search. You can check out the shop module views looking for the "$res =& eZTemplateDesignResource::instance();" settings and see what keys are set. It is these that the override systems checks against the match conditions. Cheers Bruce My Blog: http://www.stuffandcontent.com/ Follow me on twitter: http://twitter.com/brucemorrison Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish
Thiago Campos Viana	Wednesday 01 August 2007 5:53:35 pm working around you can write in the pagelayout.tpl: {if $module_result.uri\|contains("advancedsearch")} <!-- code for the advanced search layout --> {elseif $module_result.uri\|contains("shop")} <!-- code for the shop layout --> {else} <!-- code for the site layout --> {/if} eZ Publish Certified Developer: http://auth.ez.no/certification/verify/376924 Twitter: http://twitter.com/tcv_br

Author

Message

Monday 30 July 2007 7:31:34 am

Hi,

I have a site that need to present the shop and advance search with a different looks (each one with their own layout) than the default pagelayout.

Since they are modules and not nodes or classes I don't know how to make it. I try two approaches:

- I try the layout/set/(mypage_layout) but all the futher links of this pagelayout built with ezurl are reflecting the /layout/set/(mypage_layout).

- I check the sections match criteria, but we cannot associate a section to a module, so I don't have idea of how I can use this.

Are they other strategies? because none of those ones are suitable for me?

Thanks

PiR

Bruce Morrison

Monday 30 July 2007 5:00:00 pm

Hi Pierre

I've had a look at the source for content/advancedsearch (kernel/content/advancedsearch.php) and it appears that you will only beable to override based on the section.

if ( $searchSectionID != -1 )
{
    include_once( 'kernel/common/eztemplatedesignresource.php' );
    $res =& eZTemplateDesignResource::instance();
    $res->setKeys( array( array( 'section', $searchSectionID ) ) );
}

It appears that $searchSectionID can be set in the search form. I'm unsure if this effects the actual search.

You can check out the shop module views looking for the "$res =& eZTemplateDesignResource::instance();" settings and see what keys are set. It is these that the override systems checks against the match conditions.

Cheers
Bruce

My Blog: http://www.stuffandcontent.com/
Follow me on twitter: http://twitter.com/brucemorrison
Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish

Thiago Campos Viana

Wednesday 01 August 2007 5:53:35 pm

working around you can write in the pagelayout.tpl:

{if $module_result.uri|contains("advancedsearch")}

{elseif $module_result.uri|contains("shop")}

{else}

{/if}

eZ Publish Certified Developer: http://auth.ez.no/certification/verify/376924

Twitter: http://twitter.com/tcv_br

eZ debug

Timing:	Jan 18 2025 19:20:07
Script start
Timing:	Jan 18 2025 19:20:07
Module start 'layout'
Timing:	Jan 18 2025 19:20:07
Module start 'content'
Timing:	Jan 18 2025 19:20:08
Module end 'content'
Timing:	Jan 18 2025 19:20:08
Script end

Main resources:

Total runtime	0.7209 sec
Peak memory usage	4,096.0000 KB
Database Queries	59

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0055	589.0391	152.6250
Module start 'layout'	0.0055	0.0030	741.6641	39.4609
Module start 'content'	0.0084	0.7109	781.1250	585.9922
Module end 'content'	0.7194	0.0015	1,367.1172	12.1563
Script end	0.7209		1,379.2734

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0030	0.4171	16	0.0002
Check MTime	0.0013	0.1772	16	0.0001
Mysql Total
Database connection	0.0007	0.1008	1	0.0007
Mysqli_queries	0.6670	92.5232	59	0.0113
Looping result	0.0006	0.0764	57	0.0000
Template Total	0.6927	96.1	2	0.3463
Template load	0.0022	0.3078	2	0.0011
Template processing	0.6904	95.7690	2	0.3452
Template load and register function	0.0002	0.0314	1	0.0002
states
state_id_array	0.0008	0.1162	1	0.0008
state_identifier_array	0.0008	0.1068	2	0.0004
Override
Cache load	0.0019	0.2590	30	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0828	3	0.0002
Fetch class attribute name	0.0019	0.2605	5	0.0004
XML
Image XML parsing	0.0011	0.1508	3	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0017	5	0.0000
General
dbfile	0.0008	0.1121	22	0.0000
String conversion	0.0000	0.0014	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
6	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	content/datatype/view/ezxmltags/literal.tpl	<No override>	extension/community/design/standard/templates/content/datatype/view/ezxmltags/literal.tpl
2	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 16 Number of unique templates used: 7

Time used to render debug report: 0.0001 secs