Layout files their impact on the Site Editor (Internal Layout) vs Impact on Published pages

Persently I setup a more complex layout structure for display my components , before we had a very simple

1 Row format large space

Now with various areas integrated , I divided clear areas so I can drop my components into these specifed area spaces , and some what looks reasonable in site editor mode

I drop my component in square shape area , it conforms , to that shape when I put it into a thin space right rail (right gutter etc) , it sorta looks squished

However ... when I publish my page out to WWW ....or do preview mode

All that fine layout I had created just vanishes .............and components get positioned all different etc as if the layout has no "impact" on the published html page

Layout seem to hold only while I am in Edit Mode

Example:

Imagine if I was working with html table and had columns and rows , and I place a entity in that row/coloum

I have a fixed structure that houses the components which I can view from my view source window

How ever when I view my page (published html)

I do not see any entities that relate to layouts , I seem to just get the code pulled from Components

Is the layout not suppose to get published out together with the COM , HTML so the structure / positioning is some what preserved as it appears in site editor itself ???

The problem I face is , users will drop their components in layout structure in Site Editor , however when I publish that page out ... now the layout seperations do not act as a factor and the COM html just takes over and the presentation layer just looks

Not pretty

Questions:

1 . Do layouts get published along with component HTML to final HTML copy of page?

2. Can layouts be turned off to be displayed as active elements on final HTML via configuration file that

perhaps I need to turn on ?

Problem is when I do view source I only see the presence of HTML / tags coming from Components , and no indication that layout even exists to position the components on HTML page

Find more posts tagged with

Comments

Rick Poulin

blueangel wrote:
Questions:
1 . Do layouts get published along with component HTML to final HTML copy of page?
2. Can layouts be turned off to be displayed as active elements on final HTML via configuration file that
perhaps I need to turn on ?

Problem is when I do view source I only see the presence of HTML / tags coming from Components , and no indication that layout even exists to position the components on HTML page

Your final statement seems to imply that your fixed-layout.page.xsl file is broken, in that someone removed most of the logic inside of it. That said,

1) Layouts *must* be published to the runtime. This doesn't happen by magic, you have to actually publish them if they're not automatically attached to the workflow. Similarly, if your layout externalizes its CSS, then you need to push out the CSS file as well (in /iwov-resources).

2) No, you can't "turn off" the layout engine.

Is there any mention of "ls-row" in the source output on your runtime? If yes, then you might have externalized the CSS and not pushed out that file. If no, then someone buggered your fixed-layout.page.xsl (or whatever stylesheet is specified in your pagetype-config.xml.

blueangel

Thank you for your share rpoulin

Documentation States that the layout files should be located in following path

TeamSite/local/config/lib/content_center/livesite_customer_src/etc/classes/com/my-company/xsl/custom-fixed-layout.xsl(Nothing Exits in our system)
TeamSite/local/config/lib/content_center/livesite_customer_src (Nothing Exits in our system)
TeamSite/httpd/webapps/iw-preview/WEB-INF/conf/livesite_customer/pagetype-config.xml (Nothing Exits in our system)
TeamSite/httpd/webapps/iw-preview/WEB-INF/classes/com/my-company/xsl/custom-fixed-layout.xsl (Nothing Exits in our system)
TeamSite/httpd/webapps/content_center/WEB-INF/conf/livesite_customer/pagetype-config.xml (Nothing Exits in our system)
TeamSite/httpd/webapps/content_center/WEB-INF/classes/com/my-company/xsl/custom-fixed-layout.xsl (Nothing Exits in our system)

However I do not see these files in system

From Documentation:
Along with the customer-defined CSS classes, LiveSite also applies
system-defined CSS classes to the canvas,row,area,component, and othersupporting,div
structures. These system-defined classes arels-canvasls-row,ls-area,and ls-cmp
.The following supporting elements should be considered more advanced:ls-area-body,ls-fxr,ls-lqr,ls-lqa,ls-lqa-fix,ls-lqr-w,ls-lqr-e,ls-lqr-w-inner,ls-lqr-w-fx,ls-lqr-e-fx, andls-row-clr-layout.xsl

Presently in our layouts these are not generated

How or when are these generated precisely ?

a) I am looking for location path for the Layout xsl file
b) Where these "ls-" id are generated , I am just copying some existing layout files which don't have these

id's in them by default
c) How can we verify these are active so we can control the layouts once we publish the items to the "HTML published page"

Update to my own comment

What here is what I have done , I created and published a layout into system

The rows and columns look nice got 6 variations

System created a css file copy with the "ls-" ids however when I publish my page now these id references do not appear in the published HTML

So I am trying to figure out are these tags /ids only applicable to site editor mode or also when we publish to the server - if so why is my stuff not showing up in html level

Rick Poulin

Which version of the platform are you using? How much have you customized it?

I don't know what documentation you're looking at, but it sounds somewhat incorrect (and also dated, guessing v6.7?)

The non-existence of TeamSite/local/config/lib/content_center/livesite_customer_src is a big problem. Your install might be irreperably broken if you don't have this, and if you have other key folders missing like this, it could very well explain why you're seeing such odd behaviour.

You should start by getting your install validated by HP support before you keep working on individual issues, because it's really starting to sound like they're symptoms of a much larger problem.

blueangel

I suppose it was my incorrect description

TeamSite/local/config/lib/content_center/livesite_customer_src does exist however in the root level , there is only build files and folders

I was checking the 7.4 site dev rev 0 , page 335 custom xsl for rendering of layouts

The other paths however are blank

Under

TeamSite/httpd/webapps/ (No physical files / folders beyond this level)

So all path references as described in documentation do not exist

TeamSite/httpd/webapps/iw-preview/WEB-INF/conf/livesite_customer/pagetype-config.xml (Empty)
TeamSite/httpd/webapps/iw-preview/WEB-INF/classes/com/my-company/xsl/custom-fixed-layout.xsl (Empty)
TeamSite/httpd/webapps/content_center/WEB-INF/conf/livesite_customer/pagetype-config.xml (Empty)
TeamSite/httpd/webapps/content_center/WEB-INF/classes/com/my-company/xsl/custom-fixed-layout.xsl (Empty)

Also

IW-HOME/TeamSite/local/config/lib/content_center/livesite_customer_src/etc/classes/com/my-company/xsl/custom-fixed-layout.xsl(Nothing Exits)

I do not see anything under classes folder so nothing exist beyond classes folder

I am suspecting that while we have the css generated , applicable to the layout but these ids and tags are not getting to the published page etc so was trying to see how can I re-enable the "publishing" of these styles into publishing pages (html)

Rick Poulin

I guess maybe you found a documentation bug, because TeamSite/httpd/webapps hasn't been used since v6.7.2. It actually should be empty right now. Same with the livesite_customer_src folder -- there should only be a few files at the root and then etc, lib, src and web folders.

As for the com/my-company stuff (which I'm assuming was real values that you've hidden), that sounds custom so I'm not sure what your organization has done there. By default, the fixed-layout.page.xsl file won't be in the livesite_customer_src folder structure. You can find a copy in ApplicationContainer/server/default/deploy/iw-preview.war/WEB-INF/classes/com/interwoven/livesite/xsl/runtime/fixed-layout.page.xsl, and then you can copy that into the livesite_customer_src folder structure and start applying your changes.

None of this explains why your rendering isn't working properly at the moment.

blueangel

Thank you , you pointed me close enough , to xsl file where these values were being commented out

Interwoven\ApplicationContainer\server\default\deploy\iw-preview.war\WEB-INF\classes\com\interwoven\xsl\runtime

In my case the file are present here

I see some replacement logic in there

etc

    <xsl:template match="@class[contains(.,'ls-col ')]">
        <xsl:attribute name="class">
            <xsl:call-template name="string-replace-all">
                <xsl:with-param name="text" select="." />
                <xsl:with-param name="replace" select="'ls-col '" />
                <xsl:with-param name="by" select="''" />
            </xsl:call-template>
        </xsl:attribute>
    </xsl:template>
    <xsl:template match="@class[contains(.,'ls-area ')]">
        <xsl:attribute name="class">
            <xsl:call-template name="string-replace-all">
                <xsl:with-param name="text" select="." />
                <xsl:with-param name="replace" select="'ls-area '" />
                <xsl:with-param name="by" select="''" />
            </xsl:call-template>
        </xsl:attribute>

I hope this was all that was needed to reactivate the styles back into published pages etc after I modify the xsl

etc or try to publish this file out

Rick Poulin

That is most definitely not OOTB code, so someone in your organization put it there. You should find out who and why, lest you break something else.

(Topic_38773)_HideAGridRowBasedOnDataCell.png

(Topic_38773)OS_BIRT_2.6.2_HideGridRowDynamically.rptdesign