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; } } }

LSDS Runtime Page Rendering

work4u

We are seeing and issue on the LSDS runtime environment where the pages are not being rendered correctly. The pages are created in TeamSite using fix layout and components and are then deployed to the runtime using the PLC workflow. The workflow completes and the pages and dependencies get deployed successfully. However the rendered page on the runtime shows the source in the browser for images, css, etc. Not the actual page.

Find more posts tagged with

Comments

desamgopi

Make sure that code base is deployed in the runtime environment.

Thanks,
--Desam

work4u

The complete code base including the XSL, CSS, JS, page-layout templates and all custom code is deployed to the runtime. There are no errors in the log file regarding any missing files or assets.

Samir_Friend

.... However the rendered page on the runtime shows the source in the browser for images, css, etc. Not the actual page.

Can you rephrase the problem? What exactly do you see? Do you have any snapshots to attach?

Bowker

Have you looked at what's coming back to the browser? Most browsers have a developer's tool box that allows you to look at all the components to make sure all your style sheets are making it to the browser. That same tool box may help you find which styles are not being applied correctly.

work4u

Attached is the screen shot. As you can see it is not rendering the page.

Bowker

A picture says a thousand words. I've seen this before, but typically only on a single component and not on a hole page.

This looks like an XSL component that is not "matching". If you view source do you see something like:
<Properties><Data>.....

That would imply your template match="... isn't matching.

Are there any errors in the LiveSite log file?
Our livesite log file is here:
/opt/interwoven/LiveSiteDisplayServices/runtime/tomcat/logs/livesite.runtime.log

or the tomcat log file:
/opt/interwoven/LiveSiteDisplayServices/runtime/tomcat/logs/catalina.out

Samir_Friend

Attached is the screen shot. As you can see it is not rendering the page.

1. How are you attaching the CSS and JS files? Are they attached to the default.site/page or are they being directly called in component XSL?
2. Can you post the XSL for this component?

work4u

The CSS and JS files are being called through the default.site and not inline through the component. In addition in the view source there is no tag for XSL. The component is found because the component is DCR based and I can see the content from the DCR on the page.

Garth McMillan

From what I see, I'd say bowker is correct - there's probably an error in your XSL.

Check the @select attributes of your "xsl:apply-templates" elements - ensure they match correctly.

Depending on how you've set it up you may need to have a blank template (ie. doesn't output anything) that can be used as the fallback - to stop the text from the XML tree being output.

Samir_Friend

Seems to me that in your XSL, you're doing just this:

[HTML][/HTML]

instead of this:

[HTML]

[/HTML]

Yeah?

Bowker

Actually you want:

<img src="{Path to your image'}"/>

You don't nest actual tags inside other tags.