home.com
home.com/x/
home.com/xx/
home.com/xxx/
Each of these section have their own style sheets and include files
inside thier own folders. The businsess unit would not like to take
the /xx/ folder so that when a user goes to that site now, the URL
will display www.newhome.com. Giving it the appearance that it is its
own site. Has anyone done this in the past and if so what is the best
way to achieve this. We would prefer not to make it a stand alone
site. We can make the /xx/ folder the home directory for that URL at
the server level but if we do that all the links and include files
(style sheets, js files, etc) no longer work when they are called from
inside the /xx/ folder.
Any suggestions?
I think you already have the right setup. Each section having their
own style sheet. With individual publication package for each
section, section x goes to /x/, section xx goes to /xx/. I would
assume that stylesheet for section x gets published to /x/ too.
Web Server level rewrite is not needed. Assuming that resulting
publication is well sectioned, I think it is simply a pathing issue.
assuming x, xx, xxx are under its own website (in IIS, or its own
domain), and these paths are now assigned as website root.
Under Administer Publication->Project, edit general settings, "Do not
publish leading / " is not checked.
This way, all your paths are absolute relative to the root.
I hope this helps, and should you run into any trouble, please give
support a ring.
-Jian
On Dec 14, 10:24 am, shandlon <shawn.hand...@wslife.com> wrote:
> Currently we have a project that is divided up in to basically 4
> sections:
>
> home.com
> home.com/x/
> home.com/xx/
> home.com/xxx/
>
> Each of these section have their own style sheets and include files
> inside thier own folders. The businsess unit would not like to take
> the /xx/ folder so that when a user goes to that site now, the URL
> will displaywww.newhome.com. Giving it the appearance that it is its