Three individual site with common elements

Next topic

Author	Message
Ville Mattila	Wednesday 20 December 2006 4:34:16 am Hi there, I'd need to work out a site cluster featuring three independent site with different content, different design and different structure. Anyway, I would prefer to have only one eZ publish to accommodate all of them to make the administrational tasks and content mangement simple. Each site has also many common components, for example news section and common stylesheet files (partly). In general, the basic design and page layout is different in each site. I was wondering first to make three different siteaccesses (as they will be published under different subdomains) but figured out that I should configure all of them separately. Did I understand correct that each siteaccess can have own content structure at admin side? Is there any possibility to guide eZ publish to have some common stylesheets and images, like {"common_logo.gif"\|ezcommonimage) that would be independent of the current siteaccess? If I use standard {"common_logo.gif"\|ezimage} I should copy all logo images to each siteaccess design directory. Well... that's all for now. I would be happy to hear some tips and tricks how to take all performance out from eZ publish in this case. Thank you, Ville
Nabil Alimi	Wednesday 20 December 2006 6:31:36 am Hi Ville, I suggest to use a fourth siteaccess that will be your fallback. Your 3 other siteaccesses will use their own SiteDesign and will have the fourth SiteDesign as fallback. That way, anything that will be common to both sites will be stored in the fallback SiteDesign while specific elements will be in the specific SiteDesign. My blog : http://www.starnab.com/ezpublish / http://www.starnab.com/ / http://www.assiki-consulting.com eZ Publish Freelance developper. Feel free to contact me +33 674 367 057 nabil at assiki d0t fr

Author

Message

Wednesday 20 December 2006 4:34:16 am

Hi there,

I'd need to work out a site cluster featuring three independent site with different content, different design and different structure. Anyway, I would prefer to have only one eZ publish to accommodate all of them to make the administrational tasks and content mangement simple.

Each site has also many common components, for example news section and common stylesheet files (partly). In general, the basic design and page layout is different in each site.

I was wondering first to make three different siteaccesses (as they will be published under different subdomains) but figured out that I should configure all of them separately. Did I understand correct that each siteaccess can have own content structure at admin side?

Is there any possibility to guide eZ publish to have some common stylesheets and images, like {"common_logo.gif"|ezcommonimage) that would be independent of the current siteaccess? If I use standard {"common_logo.gif"|ezimage} I should copy all logo images to each siteaccess design directory.

Well... that's all for now. I would be happy to hear some tips and tricks how to take all performance out from eZ publish in this case.

Thank you,
Ville

Nabil Alimi

Wednesday 20 December 2006 6:31:36 am

Hi Ville,

I suggest to use a fourth siteaccess that will be your fallback. Your 3 other siteaccesses will use their own SiteDesign and will have the fourth SiteDesign as fallback. That way, anything that will be common to both sites will be stored in the fallback SiteDesign while specific elements will be in the specific SiteDesign.

My blog : http://www.starnab.com/ezpublish / http://www.starnab.com/ / http://www.assiki-consulting.com
eZ Publish Freelance developper. Feel free to contact me +33 674 367 057
nabil at assiki d0t fr

eZ debug

Timing:	Jan 18 2025 22:37:31
Script start
Timing:	Jan 18 2025 22:37:31
Module start 'layout'
Timing:	Jan 18 2025 22:37:31
Module start 'content'
Timing:	Jan 18 2025 22:37:32
Module end 'content'
Timing:	Jan 18 2025 22:37:32
Script end

Main resources:

Total runtime	0.7875 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0056	588.0469	152.6406
Module start 'layout'	0.0056	0.0025	740.6875	39.4766
Module start 'content'	0.0081	0.7779	780.1641	523.0625
Module end 'content'	0.7860	0.0014	1,303.2266	8.2813
Script end	0.7874		1,311.5078

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0032	0.4033	16	0.0002
Check MTime	0.0014	0.1755	16	0.0001
Mysql Total
Database connection	0.0010	0.1239	1	0.0010
Mysqli_queries	0.7435	94.4160	54	0.0138
Looping result	0.0005	0.0619	52	0.0000
Template Total	0.7532	95.6	2	0.3766
Template load	0.0024	0.3013	2	0.0012
Template processing	0.7508	95.3409	2	0.3754
Template load and register function	0.0001	0.0173	1	0.0001
states
state_id_array	0.0013	0.1590	1	0.0013
state_identifier_array	0.0012	0.1530	2	0.0006
Override
Cache load	0.0019	0.2408	15	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0005	0.0655	2	0.0003
Fetch class attribute name	0.0010	0.1258	3	0.0003
XML
Image XML parsing	0.0008	0.0997	2	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0009	3	0.0000
General
dbfile	0.0009	0.1111	16	0.0001
String conversion	0.0000	0.0008	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
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
3	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 9 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs