Sunday 23 July 2006 7:39:37 am
Hi Peter and Egil! Regarding multisite ez setup, I suggest you to create some class (Site) and one instance of it for every hosted site. That Site object will be the root node of your site instance inside the same content tree. Don't forget to setup RootNode, IndexPage, DefaultPage and PathPrefix parameters. For example: settings/siteaccess/sitex/content.ini.append.php:
[NodeSettings]
RootNode=60
settings/siteaccess/sitex/site.ini.append.php:
[SiteSettings]
IndexPage=/content/view/full/60/
DefaultPage=/content/view/full/60/
[SiteAccessSettings]
PathPrefix=sitex
Also, You will have to alter some templates which assume that the content root node is 2, like templates/menu/flat_top.tpl or the sitemap template. Just replace the hardcoded value (2) with something like ezini('NodeSettings','RootNode','content.ini'). (Shoud I post this as an enhancement to the bug section?) PathPrefix is also important because it will assure that the content of siteB can't be accessed through siteA (for example: www.siteA.com/siteB/aboutB)
Unfortunatly, PathPrefix is not documented yet, but here you can find some examples: http://ez.no/doc/ez_publish/technical_manual/3_8/reference/configuration_files/site_ini/siteaccesssettings/pathprefix Furthermore, if your hosting provider doesn't allow you to add aliases, you could maybe add some addon-domains or subdomains via availiable hosting package management tool (like cpanel or helm). If you do that, you will have one webroot directory for each site - just leave one, delete the others and create symbolic links instead which point to the "master" directory.
For example:
site1 (directory with the ez installation)
site2 -> site1/ (symbolic link)
site3 -> site1/ (symbolic link)
site4 -> site1/ (symbolic link)
... ... Vjeran
http://www.netgen.hr/eng
|