Wednesday 20 May 2009 1:12:36 am
I have a multisite setup like you are trying to set up. Short answer - its not that simple. You cannot rely on ini settings only, multiple templates have to be modified. At first I also thought setting RootNode will do it, but no, setting RootNode to anything else than 2 will mess up the system. Nobody is really sure what it is for, I think, but it should not be touched. RootNodeDepth is not enough either. It is not available on some pages, and then you get the real root, mightily confusing users.
I have each subsite as extension, there is a folder for each subsite that has folders for content (subsite root), users, media and design (contains copy of site settings object) Here is rough overview of settings overrides i have for one subsite (you will have different node id's of course)
browse.ini
AliasList[]
AliasList[content]=148
AliasList[users]=149 AliasList[media]=150
content.ini
[NodeSettings]
SubsiteRootNode=148
SubsiteUserRootNode=149
SubsiteMediaRootNode=150 (these values are added by me and used in templates where necessary, instead of relying on RootNode and RootNodeDepth, which dont work like i said)
design.ini
[SiteLookSettings]
SiteLookObjectID=252 (used to locate subsite copy of site settings object)
site.ini
IndexPage=/content/view/full/148/
DefaultPage=/content/view/full/148/
RootNodeDepth=3 DefaultUserPlacement=149 After that you need to modify pagelayout, search, menus, path line, browse template.. maybe something else im not remembering right now. My setup is 3.9 based, maybe something is improved since but i doubt. Now, ez publish would be a fantastic system if RootNode setting functioned as one would expect it to function..
Certified eZ developer looking for projects.
zurgutt at gg.ee
|