LiveSite Runtime application

Shannon/Will,

We are using Livesite production runtime 2.2.1 and it runs on BEA weblogic portal server.

It runs fine when it (runtime.war) runs as a default application in the weblogic instance. But when it is installed as an application with a context root (let's say livesite which would make my url http://ip.com/livesite instead of http://ip.com/), a lot of paths on the rendered page seem to get affected.

Example:

Please note the bold ones. It should have been /livesite/ZZZZZZSite.

Is this a known issue?

Find more posts tagged with

Comments

wscott

This is a known issue with 2.2.1. We have a fix for it, but it requires a code change that is of the "not supported, but should work" variety.

This should definitely be fixed in the next release.

magikandrea

This is a known issue with 2.2.1. We have a fix for it, but it requires a code change that is of the "not supported, but should work" variety.

This should definitely be fixed in the next release.

Hi, we have the same problem with LS 2.2.1 and WebSphere.
Can you please explain which is the code change?

Thank you very much,
Andrea

TheYann

I have the same problem, we may or may not have a context root (or context path, or whatever you want to call it). So I went ahead and did some tests with one anyway.
From the tests I've made so far, the $PAGE_LINK does not generate the path properly.

Example, if the context is foo and the site is bar, the $PAGE_LINK[MyPage] will generate /foobar/MyPage.page?
whereas it should be /foo/bar/MyPage.page?

So what is that code change so I can give that a shot as well ?