You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to include another XSLT file in my email template XSLT, but it killed the process. It seemed to resolve the path of my include file relative to the root of my Symphony build, whereas I had expected the internal paths between XSLT documents to honour the hierarchy inside /workspace (i.e. in an email template I'd expect to use ../../utilities/my-utility.xsl.)
The text was updated successfully, but these errors were encountered:
I think Symphony gets around this by creating a base XSLT document itself, then loading all other files into it (i.e. the page file). It imports this with the absolute path on disk, and I suppose all subsequent includes would then be relative to it.
However, this is not the correct behavior you would expect (and this import-statement breaks my autocomplete for this specific utility in my IDE). So you should be able to use ../../ and the extension should automagicly deal with this.
I tried to include another XSLT file in my email template XSLT, but it killed the process. It seemed to resolve the path of my include file relative to the root of my Symphony build, whereas I had expected the internal paths between XSLT documents to honour the hierarchy inside
/workspace
(i.e. in an email template I'd expect to use../../utilities/my-utility.xsl
.)The text was updated successfully, but these errors were encountered: