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

Import a xsl from the workarea in a page-layout-xsl?

RonaldV

Hi,

LS31, Sol10

is it possible to include/import a (custom) stylesheet in a page-xsl (as listed in pagetype-config)?

When you create a component your can use the resolver mechanism. If you include 'http://www.interwoven.com/custom[relative file path].xsl' it will search for the xsl in the current workarea. This same trick does not work when used in a page-xsl. Correct?

Find more posts tagged with

Comments

vpatel

What is the reason for placing your XSL in your workarea? Can you place it directly under the web app -- with the OOTB page XSLs?

karel

Hello Ronald,

(this is probably not exactly what you're looking for)

I see 2 options:
1) Use an absolute path when including/importing the xsl file. There shouldn't be any problem with including an xsl from a workarea (or staging)
2) Setup a deployment that copies your xsl from the workarea to the content_center webapp (+ ... restart the server)

RonaldV

Karel,

what I'm actually what to create is a 'generic' page.xsl. By including a page.inc.xsl from the current WA into this generic page.xsl, I can have different page-layout-xsl per branch/wa. And thus give branch A a different page-layout then Branch B/C/D/....

(And then, combine this with a custom-fixed-layout; a combination to good to be true)

With the options you mention this won't work, I think.

vpatel

Karel,

what I'm actually what to create is a 'generic' page.xsl. By including a page.inc.xsl from the current WA into this generic page.xsl, I can have different page-layout-xsl per branch/wa. And thus give branch A a different page-layout then Branch B/C/D/....

(And then, combine this with a custom-fixed-layout; a combination to good to be true)

With the options you mention this won't work, I think.

Ronald: even with the route that you are thinking you'll still have to update the page-type-config.xml file which resides under iw-home. So why not place the XSLs there as well?

Are your XSLs going to be that different per branch? Perhaps use a page-processor or a filter to inject your differences based on the site?