Wednesday 15 December 2004 12:18:21 am
I have one installation of ez with one db, but want to run two sites on it: www.mysite1.com and www.mysite2.com. Here is an extract of the node-tree:
MySites (node_id:2) |--www_mysite1.com (node_id:58 - start point for mysite1) | |- Folder1 | |- Folder2 | |-- www_mysite2.com (start point for mysite2) |- Folder3 |- Folder 4
Since I have not implemented www.mysite2.com I currently have 2 siteaccesses: mysite1_user and mysite1_admin.
In mysite1_user -> site.ini.append IndexPage=/../../58, which work nice. The node www_mysite1 (node_id 58) shows up as the frontpage.
On mysite1_admin on the other hand I changed mysite1_admin -> content.ini.append -> RootNode from 2 to 58.
At thist point I was very impressed by my self Now everything seemed to work pretty well. But... For some reason the url_aliases where wrong. What happend was that the url_alias was truncated the same number of charters as node58.name - in my case 16 - from the start. In mysite1_admin the problem was corrected when I republished the objects. In mysite1_user (which still have RootNode=2) the url_alias was still wrong.
However - if I didnt use nice urls but /content/view/full/.../ it still worked both places.
When I suspected the setting RootNode=58 in mysite1_admin to be the problem I changed it back to 2.
I'm not 100% sure if I republished the www_mysite1_com-node (58) first, but I know that nothing seems to work now... I only get the kernel error (20) saying it can't find the module www_mysite1_com - the name of the "trouble-node".
Now even /content/view/full/../ doesn't work in any of the siteaccesses. In siteaccess mysite1_admin however the nice urls work (url_alias). All other urls give the same error. This means I can't edit content, open the settings etc. All the time it tries to access the non-existing module www_mysite1_com.
Returning to content.ini.append -> RootNode=58 doesn't work, probably because I (may) republished the node www_mysite1_com when RootNode=2.
I'll be thankfull for any suggestions!
No reply yet!
You must be logged in to post messages in this topic!