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

Include HTML snippet file in Appearance XSL

msrinivas

I am trying to include a file (.html) that has some HTML snippet that I want displayed in a component. There is no transformation that is required. I am able to do this in normal XSL/XML (outside of SP) using something like:

[PHP][/PHP]

However, when I try to use the same in Appearance XSL I am not able to do it. Any pointers appreciated!

TIA!

Find more posts tagged with

Comments

vpatel

What does it mean when you say you are not able to do it? What error/unexpected behavior do you get? Any errors in the log or the UI?

With that said, my bet is that on your local instance (outside of SP) it works because the path to the included HTML file is correct and that path is not "correct" in the component context.

I would say do this via an external or a custom token -- that'll be the best way to do it. For example: have a custom token $HTML_FILE[workarea/relative/path]...
HTH!

msrinivas

This is what I have in the Appearance XSL

[PHP]

[/PHP]

The HTML file exists in the workarea of the preview site. When I do a preview there is nothing rendered. The Content XML window has just the request headers.

vpatel

This is what I have in the Appearance XSL

[PHP]

[/PHP]

The HTML file exists in the workarea of the preview site. When I do a preview there is nothing rendered. The Content XML window has just the request headers.

I don't think this will work. Most of the tokens get resolved after most of the transformation is done. $URL_PREFIX token is not different. I believe, when the XSL transformation tries to execute the xsl:copy statement, $URL_PREFIX value has NOT been resolved yet. This will cause the path to be invalid. Just for testing purposes, try putting putting in absolute path and see what you get (you may have to prefix it with file:/// -- not sure).

This is very similar to why you canNOT use tokens in XSL conditional statements (xsl:if) because the tokens are not resolved yet when the relevant XSL statement is getting executed.

HTH!

msrinivas

I think you are correct. I looked up SP Dev Guide on custom tokens. Nothing there. Where else to look for?

TIA