layout.ini SiteDesign attribute

Next topic

Author	Message
David Eriksson	Tuesday 21 June 2005 2:27:28 am Hi I'm trying to setup three different "sites" on eZpublish, using the same basic content and database, but different layouts and different parts of the data used and displayed on each site. The sites will be accessed by their own domain names, pointed to the proper URLs. Today I discovered the beauty of layout.ini and the functionality it gives that seems perfect for my needs. I can get PageLayout to work perfectly, but according to the comments in settings/layout.ini, SiteDesign should also be possible to set like for each layout, and while I believe I could do everything I need with only a new pagelayout (including different css etc), it would be a nicer solution to keep the designs separate. I haven't been able to find any documentation on this though, thus this post. I created my new directory in design/, let's call it xyz, and added [xyz] SiteDesign=xyz to layout.ini.append.php in settings/siteaccess/defaultlayout/. But it doesn't seem to work. Should I put it in override instead? Do I need to create an xyz directory in settings/siteaccess/ as well? I want it to share the settings with defaultlayout, and that is also, from what I have understood, how it should work. I'm going to keep experimenting, but if anyone has any experience of this and knows what's missing, I'd be delighted. EDIT: I decided that since I was using different domains anyhow, I just added the other two sites like I did with the first one. Probably something like that I was supposed to do anyhow. /David
Daniel Beyer	Tuesday 21 June 2005 6:50:56 am Hi David, if you want to have different designs for different siteaccess you need to add something like this to "/settings/siteaccess/YOURSITEACCESS/site.ini" [DesignSettings] SiteDesign=grayscale AdditionalSiteDesignList[]=fancyblue AdditionalSiteDesignList[]=base "SiteDesign=grayscale" means, that you want to use the design placed in "/design/grayscale". Very cool with eZ publish is, that you can define other design. that should be used, too. In my example I use two other designs "fancyblue" and "base". This means: eZ publish will first look in "/design/grayscale" for the requested "template, image, stylesheet, ... ". If it is not, it will look in "/design/fancyblue" and then in "/design/base". If the requested "template, image, stylesheet, ..." can't be found is those design, than eZ publish will fallback to the design defined in "site.ini" section "[DesignSettings]" in setting "StandardDesign", which normaly is "standard". That means, that eZ publish finally looks for the "template, image, stylesheet, ..." in "/design/standard". In my example you probably will get a grey design with a touch of blue ;) Don't forget not to override the things in "/settings/override/" if you want to have them different for each siteaccess. Otherwise the settings in "/settings/override/" will be used, because the hierarchy, how eZp includes settings is this (if you don't use extensions): 1. /settings 2. /settings/siteaccess 3. /settings/override Daniel Beyer _________________________________ YMC AG Kreuzlingen, Switzerland web: www.ymc.ch ____________________________________
David Eriksson	Wednesday 22 June 2005 3:49:22 am Yes, thank you, that's how I ended up solving it. My original question was regarding use of SiteDesign in layout.ini. The comments in the file claims it should work, but all documentation I've seen only covers the PageLayout attribute, making me suspect SiteDesign in that file is either new, or totally unused. Still, thanks for the reply. :) /David

Author

Message

Tuesday 21 June 2005 2:27:28 am

I'm trying to setup three different "sites" on eZpublish, using the same basic content and database, but different layouts and different parts of the data used and displayed on each site. The sites will be accessed by their own domain names, pointed to the proper URLs.

Today I discovered the beauty of layout.ini and the functionality it gives that seems perfect for my needs. I can get PageLayout to work perfectly, but according to the comments in settings/layout.ini, SiteDesign should also be possible to set like for each layout, and while I believe I could do everything I need with only a new pagelayout (including different css etc), it would be a nicer solution to keep the designs separate. I haven't been able to find any documentation on this though, thus this post.

I created my new directory in design/, let's call it xyz, and added

[xyz]
SiteDesign=xyz

to layout.ini.append.php in settings/siteaccess/defaultlayout/. But it doesn't seem to work. Should I put it in override instead? Do I need to create an xyz directory in settings/siteaccess/ as well? I want it to share the settings with defaultlayout, and that is also, from what I have understood, how it should work.

I'm going to keep experimenting, but if anyone has any experience of this and knows what's missing, I'd be delighted.

EDIT: I decided that since I was using different domains anyhow, I just added the other two sites like I did with the first one. Probably something like that I was supposed to do anyhow.

/David

Daniel Beyer

Tuesday 21 June 2005 6:50:56 am

Hi David,

if you want to have different designs for different siteaccess you need to add something like this to "/settings/siteaccess/YOURSITEACCESS/site.ini"

[DesignSettings]
SiteDesign=grayscale
AdditionalSiteDesignList[]=fancyblue
AdditionalSiteDesignList[]=base

"SiteDesign=grayscale" means, that you want to use the design placed in "/design/grayscale". Very cool with eZ publish is, that you can define other design. that should be used, too. In my example I use two other designs "fancyblue" and "base".

This means:
eZ publish will first look in "/design/grayscale" for the requested "template, image, stylesheet, ... ". If it is not, it will look in "/design/fancyblue" and then in "/design/base". If the requested "template, image, stylesheet, ..." can't be found is those design, than eZ publish will fallback to the design defined in "site.ini" section "[DesignSettings]" in setting "StandardDesign", which normaly is "standard". That means, that eZ publish finally looks for the "template, image, stylesheet, ..." in "/design/standard".

In my example you probably will get a grey design with a touch of blue ;)

Don't forget not to override the things in "/settings/override/" if you want to have them different for each siteaccess. Otherwise the settings in "/settings/override/" will be used, because the hierarchy, how eZp includes settings is this (if you don't use extensions):
1. /settings
2. /settings/siteaccess
3. /settings/override

Daniel Beyer
_________________________________
YMC AG
Kreuzlingen, Switzerland
web: www.ymc.ch
____________________________________

David Eriksson

Wednesday 22 June 2005 3:49:22 am

Yes, thank you, that's how I ended up solving it.

My original question was regarding use of SiteDesign in layout.ini. The comments in the file claims it should work, but all documentation I've seen only covers the PageLayout attribute, making me suspect SiteDesign in that file is either new, or totally unused.

Still, thanks for the reply. :)

/David

eZ debug

Timing:	Jan 19 2025 07:05:45
Script start
Timing:	Jan 19 2025 07:05:45
Module start 'layout'
Timing:	Jan 19 2025 07:05:45
Module start 'content'
Timing:	Jan 19 2025 07:05:46
Module end 'content'
Timing:	Jan 19 2025 07:05:46
Script end

Main resources:

Total runtime	1.3914 sec
Peak memory usage	4,096.0000 KB
Database Queries	57

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0081	589.1563	152.6250
Module start 'layout'	0.0081	0.0034	741.7813	39.4609
Module start 'content'	0.0115	1.3780	781.2422	545.4609
Module end 'content'	1.3895	0.0018	1,326.7031	12.4766
Script end	1.3913		1,339.1797

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0038	0.2733	16	0.0002
Check MTime	0.0015	0.1095	16	0.0001
Mysql Total
Database connection	0.0016	0.1119	1	0.0016
Mysqli_queries	1.3310	95.6631	57	0.0234
Looping result	0.0007	0.0470	55	0.0000
Template Total	1.3461	96.7	2	0.6730
Template load	0.0023	0.1624	2	0.0011
Template processing	1.3438	96.5785	2	0.6719
Template load and register function	0.0002	0.0166	1	0.0002
states
state_id_array	0.0017	0.1189	1	0.0017
state_identifier_array	0.0037	0.2625	2	0.0018
Override
Cache load	0.0019	0.1394	28	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0007	0.0477	2	0.0003
Fetch class attribute name	0.0018	0.1307	4	0.0005
XML
Image XML parsing	0.0008	0.0562	2	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0009	4	0.0000
General
dbfile	0.0020	0.1419	16	0.0001
String conversion	0.0000	0.0007	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
7	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	content/datatype/view/ezxmltags/literal.tpl	<No override>	extension/community/design/standard/templates/content/datatype/view/ezxmltags/literal.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.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: 17 Number of unique templates used: 7

Time used to render debug report: 0.0001 secs