nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

NSAPI configuration

johnjamesmarsh

iPlanet 6.0
TS 6.1
Solaris 5.8

We have a Teamsite installation with Teamsite running on port 80 and the customer web site running on port 81/443. The whole installation is installed following the manuals but when you browse to http://new_site:81 or https://new_site (or http://new_site:1080) HTML page is fine but the images don't appear.

I have raised a support case with Interwoven and they say we are using Teamsite outside of it's intended use. Does anyone else use Teamsite like this? Isn't that why we spent all that money on it?

Thanks

John

Find more posts tagged with

Comments

nipper

Yes you are using TS outside of it's intended use.

Also, you are not even using TS when you go to http://newsite:81/

If you want to use that convention then you can only use relative paths for your images.

By using that convention, your link goes to /images/hi.jpg but the loaction is really /iw-ount/default.main/branch/WORKAREA/workarea/images/hi.jpg

You have 2 choices, make all your links relative or create a webserver with the docroot where /images will work.

I suggest creating a docroot outside of TS, use OpenDeploy to move the files outside and point Apache to it.

johnjamesmarsh

The way the system was installed/configured 4 years ago was that Teamsite and the customer web server used the same webroot. We moved to 6.1 and that requires that Teamsite has exclusive use of port 80.

The reason we have this is that we have TBI (Teamsite Broadvision Integration). We have had to move the weberver onto port 81 as Teamsite now takes port 80. The image virtualisation was failing with file not found errors but if you copied the image location and pasted it into your browser it would be fine.

As a crazy aside it all works fine when using FireFox as the browser. Only IS exhibits the problem!

Anyone got any ideas as to how we can reproduce the 4.5.1 functionality on 6.1?