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

fixed layout

bturns

Hi,

TS 6.7.2

I've created a custom fixed layout located at

....WORKAREA/shared/iw/config/fixed-layout/home_page.xml

livesite then generated a css

....WORKAREA/shared/iwov-resources/fixed-layout/home_page.css

and now inserts this css into the head of all of my html pages.

I really don't want this css to be part of the page. Is there anyway to stop livesite from inserting this css into the html.

Thanks,

Brian

Find more posts tagged with

Comments

interDev

Hi,

TS 6.7.2

I've created a custom fixed layout located at

....WORKAREA/shared/iw/config/fixed-layout/home_page.xml

livesite then generated a css

....WORKAREA/shared/iwov-resources/fixed-layout/home_page.css

and now inserts this css into the head of all of my html pages.

I really don't want this css to be part of the page. Is there anyway to stop livesite from inserting this css into the html.

Thanks,

Brian

The fixed layout is actually achieved through this css file only, if there will be no home_page.css, there will be no fixed layout. Technically you can exclude the css file by making changes in fixed layout XSL file at the backend.
What exactly is your concern? why you dont want to include this css file? there might be some other solutions to your actual problem.

bturns

if the css file is what determines the fixed layout then what is the ....WORKAREA/shared/iw/config/fixed-layout/home_page.xml
for?

I'm trying to have the site publisher preview look correct. So, we use a fixed layout to get the components in the correct location. However, the home_page.css overrides some of our own css settings so the page doesn't quite look right when it's displayed on the webserver.

interDev

if the css file is what determines the fixed layout then what is the ....WORKAREA/shared/iw/config/fixed-layout/home_page.xml
for?

I'm trying to have the site publisher preview look correct. So, we use a fixed layout to get the components in the correct location. However, the home_page.css overrides some of our own css settings so the page doesn't quite look right when it's displayed on the webserver.

Lets take a step back here. The home_page.css file is generated from the specifications described in home_page.xml file. Whenever content is rendered on webserver, home_page.css is the used and NOT home_page.xml.

home_page.css cannot overwrite your own styles because this is the first css file included in the page header, custom build css files are included after this. So your custom css file can overwrite styles described in home_page.css and not otherway round (unless you have done some real customizations in your layout XSL files to change the order of these css files).

What specific styles problems are you facing?

bturns

originally we were not deploying our home_page.css. we wanted the home_page.css to only be used during preview. However, our analytics folks started complaining about the not found error because the home_page.css file was still referenced in our output html.

so, one question I have....is it possible to exclude the home_page.css from our output file?

We recently started deploying out the home_page.css. However, the pixel width's in the home_page.css were off and the page started creating some weird spacing.

We've since gone into the home_page.css and updated the pixel widths. However, Ideally we'll like to have the fixed-layout css only be used in TeamSite and use our own custom css file be used on the webserver.

Is it possible to exclude the fixed-layout.css from being placed in the generated html?

Adam Stoller

You could always add a step to the workflow to post-process the generated HTML to remove that particular CSS reference, before the deployment.

jbonifaci

You could also create a custom page xsl and update the xsl to not output that css reference.

You should be able to find plenty of info on this, but basically it is done using this file:

\Interwoven\TeamSite\local\config\lib\content_center\livesite_customer_src\etc\conf\livesite_customer\pagetype-config.xml

And placing your custom page xsl here:

\Interwoven\TeamSite\local\config\lib\content_center\livesite_customer_src\etc\classes\com\interwoven\xsl\runtime

And obviously running a build.

~Jeff

interDev

originally we were not deploying our home_page.css. we wanted the home_page.css to only be used during preview. However, our analytics folks started complaining about the not found error because the home_page.css file was still referenced in our output html.

so, one question I have....is it possible to exclude the home_page.css from our output file?

We recently started deploying out the home_page.css. However, the pixel width's in the home_page.css were off and the page started creating some weird spacing.

We've since gone into the home_page.css and updated the pixel widths. However, Ideally we'll like to have the fixed-layout css only be used in TeamSite and use our own custom css file be used on the webserver.

Is it possible to exclude the fixed-layout.css from being placed in the generated html?

Are you generating static HTML or using LSDS on webserver?

If generating HTML,you can exclude CSS by adding a step in workflow to remove the specific css file from generated HTML.

If using LSDS,you will have to modify your page XSL file to exclude specific CSS file (do this only on your LSDS webserver).

Your design doesnt look right to me. If you dont want to use fixed layout on webserver why are you using it while previewing? Why dont you use open layouts in that case in Teamsite and let you custom build CSS control everything on the page (on teamsite and webserver both).

susheel

just emtpy the css file remove everything present in it. it won't effect the layout it will work as it should.