I have a new install of 4.5.2 running on a development server using IIS 7. I am trying to run two sites from one install, one for .com and the other for .org. My document structure is:
Content -CrimsonCom -Page -CrimsonOrg -Page
Each site has its own master page tree and I have set useDomainPrefixes to true. In the control panel, the link to document points to /crimson/crimsoncom and /crimson/crimsonorg as would be expected.
The problem occurs with the pages under the respective site home pages the url for each 'Page' is /crimson/page rather than /crimson/crimsonorg/page. What that means is that I can't see the pages to work on them.
I'd appreciate any help so I don't have to throw the site up live to see what it looks like.
Multiple site question
I have a new install of 4.5.2 running on a development server using IIS 7. I am trying to run two sites from one install, one for .com and the other for .org. My document structure is:
Each site has its own master page tree and I have set useDomainPrefixes to true. In the control panel, the link to document points to /crimson/crimsoncom and /crimson/crimsonorg as would be expected.
The problem occurs with the pages under the respective site home pages the url for each 'Page' is /crimson/page rather than /crimson/crimsonorg/page. What that means is that I can't see the pages to work on them.
I'd appreciate any help so I don't have to throw the site up live to see what it looks like.
Jon
Hi Jon,
You might try setting this setting in the web.config from true to false: umbracoHideTopLevelNodeFromPath
Or, leave it set to true and add one more level above the crimsoncom & crimsonorg nodes.
(Some) info here: http://our.umbraco.org/wiki/reference/webconfig
Also, where is /crimson/ coming from, are you running this in a virtual directory?
-Tom
Thanks, Tom.
Crimson is coming from a web application under 'Default Web Site' on a local 2008 server. So:
All I did was create it as a web project using Visual Studio. I'll try the other in the morning.
Jon
Gotcha - did that fix your issue?
That fixed it. Thanks very much Tom
is working on a reply...