CSS display issues in Management Server 10

[Tim McAuliffe]

Hi Everyone,

We're having a problem with CSS not being displayed in a project we've
exported from CMS 7.5 into CMS 10. The CSS is displayed correctly in
Smart Tree-Preview and Smart Edit-Redlining modes but it doesn't
display in Smart Edit-RedDot or Smart Edit-Preview modes.

Turns out that the display handlers are different for these modes. The
template for Smart Tree-preview and Smart Edit-Redlining is /CMS/
ioRD.asp whereas the display template that doesn't work is /CMS/
WebClient/PreviewHandler.ashx. So on first impressions it looks like
it's a new .NET display handler that's having problems.

We have followed the release notes advice on avoiding certain names
such as RD, RedDot etc as well as the advice on RDExecute and
PreExecute settings. Has anyone else experienced this issue?

[Henry Lu a.k.a. Javahand]

Tim--

 

I had one project built in 7.5. After upgrading the server to 10, the project went completely blank in SmartEdit.

 

My suspicion -- albeit unconfirmed -- is that the project has "global" preexecution element written in JScript.

 

The owner of the project did not see much to gain from version 10 and has decided to stay with 7.5; as a result, I have not got a chance to get to the bottom of it.

 

Henry Lu

--
646-807-8683

[El Pollo Loco]

From what I was told there is a problem with the z-index in SmartEdit.
You may want to play around with setting the z-index to different
values.

On Jul 29, 2:01 pm, "Henry Lu a.k.a. Javahand" <javah...@gmail.com>
wrote:

> Tim--
>
> I had one project built in 7.5. After upgrading the server to 10, the
> project went completely blank in SmartEdit.
>
> My suspicion -- albeit unconfirmed -- is that the project has "global"
> preexecution element written in JScript.
>
> The owner of the project did not see much to gain from version 10 and has
> decided to stay with 7.5; as a result, I have not got a chance to get to the
> bottom of it.
>
> Henry Lu
>

[Tim McAuliffe]

Thanks for the replies. We've now received confirmation from OpenText
that it's a bug and due to be fixed in August.

If anyone else has this issue, the problem is that in CMS 10 there are
2 display handlers that run in different directories: /cms and /cms/
WebClient.

We were linking to our CSS like this:
<link href="<%con_LayoutCSS%>" rel="stylesheet" type="text/css" />
which produced code like this:
<link
href="RDTemp_4AA9CBD10E7345FE95B24C6FBA1AF9F2_0BFFC5971CCB4B18883D4D3877C540FF.css"
rel="stylesheet" type="text/css" />

So, because the CSS link is relative to the current directory, but the
display handlers are in 2 different directories it's not going to work
in both.