RootNode and Bread-crumbs

Next topic

Author	Message
Lachy Laycock	Tuesday 25 November 2003 8:51:40 am Hi, I have recently discovering the wonders of creating multiple sites that can share cascading template sets (with AdditionalSiteDesignList[]), and have uncovered a problem... My Web host only allows me a fixed number of MySQL DBs and so I have been looking for a way to combine multiple sites with one DB (i believe this was possible for versions <3.2)... My Solution: Use the settings variable NodeSettings->RootNode to set the top page. But alas it doesn't seem to work. So I have managed to create a few work arounds: 1. In the settings/siteaccess/mysite/site.ini.append file I set the DefaultPage and IndexPage nodes under my root dir (2) that will be the rootNode for each site. This works fine. 2. Change template links that point to '/content/view/full/2/' to concat("/content/view/full/",ezini('NodeSettings','RootNode','site.ini') 3. Hack the Bread-Crumbs (Path) display to show the RootNode value as 'Home' (NodeID: 2). This last step I have been unable to do successfully. I have tracked the source down to the function 'fetchPath' in ezcontentobjecttree.php, and have used the following dirty hack: $nodePath = $this->attribute( 'path_string' ); [line: 1823] to $nodePath = $this->attribute( 'path_string' ); $nodePath = str_replace('/2/', '/', $nodePath); simply removing the rootNode fixes this but I suspect the rabbit hole goes a little deeper than this and might break something somewhere else... Does anybody have any ideas or suggesstions as to how this might be accomplished in a less destructive manner? Regards, Lachy
Marco Zinn	Wednesday 26 November 2003 3:14:42 pm Hm, I'm not sure, if i got your setup. I suspect, that -because your MySQL DB count is limited- you want to put all content into on MySQL DB (for different sites) and let all content start "one level below root", so your sites "virtual root folders" are all children of root (node 2). Right? When: Why do you want to show the "real" Root-Folder (2) anyway? Any click on that will have your visitors go up one level to much and see all websites... Better hide the "root"-Folder from path (see my other posting http://ez.no/developer/ez_publish_3/forum/setup_design/toppath_without_root_folder#msg39292) and start with your "virtual home". Besides that: I think, no version of ezP supports multiple websites in one MySQL DB. In 3.1, it was possible to install multiple "designs" (now: "Packages") into one DB, while the new ez-3.2-installer does not support this. Note: IMHO, if you really want distinct sites, you will need multple DB's.... how do you want to restrict the search engine, the admin interface etc, when everything is in one large "content tree"? Marco http://www.hyperroad-design.com

Author

Message

Tuesday 25 November 2003 8:51:40 am

Hi,

I have recently discovering the wonders of creating multiple sites that can share cascading template sets (with AdditionalSiteDesignList[]), and have uncovered a problem...

My Web host only allows me a fixed number of MySQL DBs and so I have been looking for a way to combine multiple sites with one DB (i believe this was possible for versions <3.2)...

My Solution:
Use the settings variable NodeSettings->RootNode to set the top page.

But alas it doesn't seem to work. So I have managed to create a few work arounds:

1. In the settings/siteaccess/*mysite*/site.ini.append file I set the DefaultPage and IndexPage nodes under my root dir (2) that will be the rootNode for each site. This works fine.

2. Change template links that point to '/content/view/full/2/' to concat("/content/view/full/",ezini('NodeSettings','RootNode','site.ini')

3. Hack the Bread-Crumbs (Path) display to show the RootNode value as 'Home' (NodeID: 2).

This last step I have been unable to do successfully.

I have tracked the source down to the function 'fetchPath' in ezcontentobjecttree.php, and have used the following dirty hack:

$nodePath = $this->attribute( 'path_string' ); [line: 1823]

$nodePath = $this->attribute( 'path_string' );
$nodePath = str_replace('/2/', '/', $nodePath);

simply removing the rootNode fixes this but I suspect the rabbit hole goes a little deeper than this and might break something somewhere else...

Does anybody have any ideas or suggesstions as to how this might be accomplished in a less destructive manner?

Regards,
Lachy

Marco Zinn

Wednesday 26 November 2003 3:14:42 pm

Hm, I'm not sure, if i got your setup.
I suspect, that -because your MySQL DB count is limited- you want to put all content into on MySQL DB (for different sites) and let all content start "one level below root", so your sites "virtual root folders" are all children of root (node 2). Right?
When: Why do you want to show the "real" Root-Folder (2) anyway? Any click on that will have your visitors go up one level to much and see all websites...
Better hide the "root"-Folder from path (see my other posting http://ez.no/developer/ez_publish_3/forum/setup_design/toppath_without_root_folder#msg39292) and start with your "virtual home".

Besides that: I think, no version of ezP supports multiple websites in one MySQL DB. In 3.1, it was possible to install multiple "designs" (now: "Packages") into one DB, while the new ez-3.2-installer does not support this.

Note: IMHO, if you really want distinct sites, you will need multple DB's.... how do you want to restrict the search engine, the admin interface etc, when everything is in one large "content tree"?

Marco
http://www.hyperroad-design.com

eZ debug

Timing:	Jan 18 2025 18:34:59
Script start
Timing:	Jan 18 2025 18:34:59
Module start 'layout'
Timing:	Jan 18 2025 18:34:59
Module start 'content'
Timing:	Jan 18 2025 18:34:59
Module end 'content'
Timing:	Jan 18 2025 18:34:59
Script end

Main resources:

Total runtime	0.7254 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.0068	587.9141	152.6250
Module start 'layout'	0.0068	0.0038	740.5391	39.4453
Module start 'content'	0.0105	0.7133	779.9844	529.1250
Module end 'content'	0.7239	0.0015	1,309.1094	12.1641
Script end	0.7253		1,321.2734

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0035	0.4810	16	0.0002
Check MTime	0.0014	0.1978	16	0.0001
Mysql Total
Database connection	0.0013	0.1762	1	0.0013
Mysqli_queries	0.6748	93.0225	54	0.0125
Looping result	0.0006	0.0794	52	0.0000
Template Total	0.6907	95.2	2	0.3453
Template load	0.0022	0.3052	2	0.0011
Template processing	0.6885	94.9089	2	0.3442
Template load and register function	0.0001	0.0196	1	0.0001
states
state_id_array	0.0020	0.2695	1	0.0020
state_identifier_array	0.0016	0.2145	2	0.0008
Override
Cache load	0.0018	0.2548	30	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0007	0.1032	2	0.0004
Fetch class attribute name	0.0014	0.1884	3	0.0005
XML
Image XML parsing	0.0006	0.0774	2	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0017	3	0.0000
General
dbfile	0.0008	0.1100	16	0.0000
String conversion	0.0000	0.0013	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
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
4	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: 14 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs